It also doesn't talk about using Instance memory, which is a HUGE part of my caching strategy. Even from a beginners guide I'm not sure this is an article I would promote, I think more people will be unhappy with this solution than will benefit from it.
-----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer Sent: Saturday, October 08, 2011 2:21 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] App Engine Weekly Community Update #11 On Sat, Oct 8, 2011 at 5:16 AM, Johan Euphrosine <pro...@google.com> wrote: > > Nice Article about caching strategies for App Engine apps by +Chris > Bunch > http://www.byzantinereality.com/2011/8/Two-Caching-Strategies-for-App- > Engine-apps That page doesn't seem to allow comments, so I'll have to rant here: This caching strategy is a terrible idea. Trust me, it's taken a long time to work out the kinks in Objectify's transparent memcache. This caching strategy will go out of sync under contention. You need to use CAS operations to avoid race conditions. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
