> > The whole point of memcache is using it instead of datastore for > performance reasons. > > Well yes, kinda.
But an important point its its 'best effort'. Even with 'dedicated memcache' you can't *rely *on data staying there. Your cache may be lost at any point (say your app moves between datacenters) or even if Google simply moves memcached to a new server. Its a normal part of operation that data is evicted/lost ... use it when you can, but your app should cope just fine if its data is not in memcache (albeit a bit slower) (ie filling it via cron is not a good way to use it) Store your data in the datastore, just cache it memcache as well. App works if memcache is available or not. Most of the time memcache will be available, so you won't pay for datastore reads. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAJCAUuKoNj05vpLMybBu8LLchmg7uDNnv0LE4bS1xRrwg%2BqJmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
