Maintenance is nothing new. It has been around since day 1. Today we have a choice, so if you are that worried about maintenance use HR. Consistency can be dealt with by using ancestor queries. Also, remember a .get() will have Strong Consistency, only queries must have ancestors to have strong consistency. Also, in my experience almost every query has strong consistency within a few hundred milliseconds... So for me it was a no-brainer. I guess high usage apps may be bothered by the pricing, however I can see no other reason to not switch to HR asap.
my 2 cents On Apr 7, 8:52 pm, Kyle Mulka <[email protected]> wrote: > PS: I'm also worried about all the extra code I'm going to have to > write to deal with the fact that the datastore may be inconsistant at > times. > > On Apr 7, 9:50 pm, Kyle Mulka <[email protected]> wrote: > > > > > > > > > On Apr 7, 10:20 am, "Ikai Lan (Google)" <[email protected]> wrote: > > > > Yes, we'd love to do that at some point in the future - pick a general > > > area > > > where your apps would exist, and we'd run them from those nodes. I suspect > > > that if we ever did this feature and you wanted to move to a new cluster, > > > that you would have to run the datastore migration tool (similar to what > > > it > > > would take to move from MS -> HR), and if you're going to do this, why not > > > just move to high replication? > > > I'm not that worried about running the migration tool. Should I be? > > I'm worried about the eventual consistency model of the high > > replication datastore. I want a user of our app to be able to create > > an object in the datastore and then be able to read it right away. > > > -- > > Kyle Mulka > > Co-Founder, DealSavanthttp://www.dealsavant.com -- 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.
