If your Instance cost is too high it means you aren't using API's enough. A well designed app is going to be close to 50% API, a superbly designed App will be 85% API when you look at the logs and see ms=42 cpu_ms=2 api_cpu_ms=14 you know you are doing it right.
Again this means not using heavy frame works, but instead creating proper datastore queries the right way, and optimizing your code for the platform. Doing lots of optimizations does create lockin, but that is the trade off of optimizing for "Instance cost" the same is true of AWS or OpenCloud technologies. The more you Optimize the more you have lockin. Reliability is not spotty unless you are building apps that take more than 35s per request. If you are doing that, your users already hate you and won't be surprised when you are down. Backend can save you a ton of money use them. Use them often. One trans per entity per second is only an issue if you don't know how to use shards and build a write buffer, (which you should have anyway for managing contention). We are now handling 1 billion writes a day in an app. In some cases logical entities are being updated 15 times per second. We are having no trouble. We did end up building our own memcache-like server to help with that, so to get to those numbers you need a backend. It is not "All sunshine and unicorns" lack of naked domains, and Apps For Domains weird rules are a pain in the ass. -- 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.
