Thanks Barry. Yes i do need to do some validations. So it will leave the other instances cache to stay as it is until the instance shutdown. All things leading me to kill instance cache for this operation.
So i will better restrict my instance caching with constants and enums. Thanks Guys for clearing my doubt. On Monday, March 17, 2014 6:40:18 PM UTC+5:30, barryhunter wrote: > > > > > On 17 March 2014 12:59, Bharath Kumaar <bharathkuma...@a-cti.com<javascript:> > > wrote: > >> Thanks Stephan. Memcache is my second level. My level of retrieving data >> will be Instance Cache, Mem cache and then Datastore. But from your reply i >> guess i have to go with mem cache directly and then DataStore. As mine is >> kind of single page application, i thought of adding Instance caching. >> > > You can add instance caching well if you want. > > Just that its (more) optimistic. It might not be in the instance cache > (because the user has happened to hit a different instance), in which case > can be got from memcache. If not memcache than datastore. > > ie hit ratio will be lower than memcache, but hopefully big enough that > worth it. > > ... but it does bring another issue. As there are multiple instances, > invalidation doesn't work. You can invalidate (or update!) the local > instance cache, but it wont(!) update the other instance caches. > Depends on your usecase if need invalidation and/or updating of caches. > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
