I think you are missing the point. The goal of this App Engine way is to *force* you to use cache, You only have to query once when the data is modified, then you store the results on a server cache and you can serve as many page views you want with no further access to the datasore, Super fast and with no extra charge.
But doesn't it mean I'll have lots of data in cache? Yes, but that is the point: no matter how fast HRD can be, a replicated database will never be as fast as a standalone RDBMS for most trivial queries. So, it is not because Google wants profit more on your queries, but the fact is that you can never have an efficient webapp or webpage based on a cloud-based service if you don't do a lot of caching. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/cTg5NdWsadgJ. 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.
