To me as a developer this kind of optimization seems to be absurd. Caching is something the datastore layer is supposed to take care of. Why am I supposed to create my own caching framework on top of datastore while dealing with single/multi key lookups? Yes, it will save me costs with the current pricing schema. But theres really no technical ratio behind it. Are we now at the point where we design our apps for a certain pricing model rather than a specific PAAS-stack? What if Google decides to bill memcache lookups? We start caching in heap?
-- 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/-/bHNxfvBsXCcJ. 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.
