Thank you for this! A few notes:
1. If you do "ancestor queries" where you set an entity group root, that query will be strongly consistent. 2. Get by ID happens transactionally. Currently, I think we only allow each request to have 5 outstanding transactions, so if you do a batch get by ID of, say, 500 entities, this will run about as fast as if you performed 100 fetches serially. To get around this behavior, set the "eventual consistency" flag to true in your datastore client. Note that this will cause your data to exhibit eventual consistent behavior like in point 1 - clever Memcaching should mostly hide the issue from users. We're working on ways to improve this, but for the time being you'll need to be aware of it. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Thu, Jun 23, 2011 at 10:44 AM, Greg <[email protected]> wrote: > Hi - > > I have previously posted about a MS-HR migration how-to here: > > > http://neogregious.blogspot.com/2011/04/migrating-app-to-high-replication.html > > I've now followed up with some lessons learned from the migration: > > > http://neogregious.blogspot.com/2011/06/high-replication-migration-lessons.html > > Hope you find them useful. > > Cheers > Greg. > > -- > 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.
