On Thu, May 26, 2011 at 2:32 AM, Rohan Chandiramani
<masterxr...@gmail.com> 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?

That's the vague principle, but without knowing more about your
application, it's really hard to say.  Depending on how durable your
writes need to be, you might be able to get away with multiple updates
to memcache with a delayed write to the datastore.

Also, the pricing model of GAE is about to change in ways that have
not been defined yet (ie, what exactly constitutes a "datastore
operation").

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.

Reply via email to