I'd say memcache generally has a much higher value when you're very read heavy. But, one thing to consider is that even if you're writing to the datastore in most requests, memcache might can still save you time fetching entities from the datastore. However, as Jeff noted, keeping your memcache and datastore in-sync is going to be quite hard.
Robert On Thu, May 26, 2011 at 05:32, Rohan Chandiramani <[email protected]> wrote: > Hi, > So to clarify on the memcache principal, > High reads - low writes, memcache is a good option. > High reads - high writes, might as well only use the datastore? > Thanks, > Rohan > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > 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. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
