You can increase entity update limit by using MS datastore and shards. This way you can have a rate of 100/s for your logical single instance. But don't forget that MS is not reliable, neither memcache or backends. You will face a nightmare trying to make it work fast and reliable. On Dec 20, 2011 7:38 PM, "Kaan Soral" <[email protected]> wrote:
> My initial idea was to keep everything in one datastore entity, in a blob > property, players would post changes to this entity, and when they request > the game state, they would also get contents of this item > But I totally forgot about the 5/s datastore write limit for a single > entity > > So even with short-polling, it wouldn't work > > Backend + short-polling sounds like a great idea now to me, although I > didn't quite get the git idea > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/vobs7E5lllYJ. > 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.
