On Wed, May 18, 2011 at 4:01 PM, Brandon Wirtz <[email protected]> wrote: > Regarding differences in pricing based on Differences in Latency: > > Welcome to the real world.
This isn't quite right. Yes, there is a real-world cost to latency - but due to a poor design decision by GAE's engineers, that cost is at least two orders of magnitude higher than it is on any other platform. Google has sheltered us from not only the cost of their single-threaded python system, but also the knowledge that the system is as inefficient as it is. I built a GAE/Python backend for a client whose "internet bill" ends up being ~$10/mo. I'm very concerned that this bill is about to go to $100-$200/mo (even with the price halved) for a system that would still be $10/mo if I had written it in Java like all my other GAE apps. Hell, this guy's app could even run on a simple LAMP stack - it peaks around 4 hits per second. If my client's bill spikes like this, I'm going to look like a total asshole. And I really shouldn't - if I had known the technology limitations ahead of time, I could have worked around it (or simply not used appengine for that project). I don't mind that GAE's price reflects actual cost of services as long as 1) I know what that is ahead of time and 2) the cost is reasonable - and a single-threaded service layer is simply not an adequate use of precious memory in this day and age. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
