Instead of ranting "google broke it",
it might be more productive if you:
- identify the type of app you are building
- use cases
- API calls
- number users
- typical transactions
- consistency requirements
- etc
then offer some suggestions on how google
could support your use ca
>
> "Instead, it looks to me that they just thought of some ideas that *might*
> make
> things more efficient, but guessed wrong."
This is what I think as well. It's clear that the Java version at least
works nothing like how GAE was originally presented.
--
You received this message because
Pricing should be as follows:
Calculate a price of resources using the demand / availability of
those resources in the cloud:
- if Google has more of resource X than users demand, the price for
that resource would go down and free quota up.
- if users demand more of resource X than Google has, th
Users who need a highly predictable bill could pre-allocate X
resources for $ ("special deal" like $9 / month). It tells the
supplier: produce this much at a given future date for the now agreed
price. Supplier profits from planing stability, buyer profits from
price and supply stability.
Incentiv
Amazon does something like this for its excess capacity:
http://aws.amazon.com/ec2/spot-instances/
...but it's just for excess capacity. I wouldn't want this kind of
behavior for my core usage because it would make my bill highly
unpredictable. And it does not incentivize Google to add more
res
