I don't see how this is helpful in the GAE environment. The "aggregate root" he refers to is really just an ancestor in GAE. So you make the player its own entity group, and the updates will be ACID, and all is well. Except that you are stuck with the 1 sec/update, which is probably fine anyway. (Probably better than a synchronous poll/wait, which, frankly, sounds kinda nuts.)
On Dec 7, 2011, at 5:48 AM, Brandon Wirtz wrote: > This is a great article on building scalable apps when the eventual > consistency is to slow for your transaction rate. > > http://blog.ploeh.dk/2011/12/07/PolymorphicConsistency.aspx > > The code examples are for .Net but the logic works the same as it would in > GAE. > > Ploeh is a smart guy. (not as smart or good looking as me) but he documents > his code better and he proof reads his articles more thoroughly so that makes > him a good guy :-) > > > > > -- > 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.
