CODEWITHSUNDEEP
google-app-engine
Roger Gilbrat
Roger Gilbrat

Reputation: 3845

Google App Engine and data replication with multiple instances

I'm using the Google App Engine as the backend for an iOS game that was just released.

Through that act of playing the game, players create levels and then those are shared with their friends and the world at large. GAE is used to store and retrieve those levels. GAE also Manages player's high scores since they are more complex than Game Center can handle.

As a whole, GAE works great. I like how GAE spins up new instances as they are needed without me having to constantly monitor load. For this game, GAE is running around 10 instance and serving around 8 queries a second.

But there is a small problem.

I've noticed that sometimes players will get on the high score table twice. This should not be possible since I remove any old scores before putting up the new scores (this is done in one query to GAE).

After some testing and poking around, it seems that what is happening is that a player will get a high score and instance 1 handles the removing of the old score and the adding of the new one. The player then gets a new high score, but this time instance 4 is the one that handles the request and it doesn't know about the other score yet.

At their fastest, it might take a player 10 seconds to get a new high score. It was my understanding that the replication of data only took 2 or 3 seconds.

I never saw this problem during testing because load rarely caused 2 instances to be started.

Does this seem like a plausible explanation for what is happening and how data is stored for each instance?

Is there a way to guarantee that data added, deleted or altered in one instance will be available in another? High scores are not "mission critical", so I'm not too worried about it, but I would like to use GAE for some more complex situations where it is very important that data is consistent.

Is that possible with GAE, or should I be looking at other solutions?

Upvotes: 1

Views: 334

Answers (1)

Sebastian Kreft
Sebastian Kreft

Reputation: 8199

It is possible to guarantee that data will be consistent across all data centers (strong consistency). You need to use ancestor queries to achieve it. However, doing so poses a restriction on how many write per seconds you can achieve. Currently the limit is 1 write per second.

If the write limit is too slow for you, one alternative is to add a cache layer. So you will still be using the eventual consistency model, but you will mix those results with the ones in memcache.

See the doc Structuring for Strong Consistency for further details.

Upvotes: 2

Related Questions