Goodbye Google App Engine (GAE)
[…] developing on GAE introduced such a design complexity that working around it pushes us 5 months behind schedule. Now that we had developed tools and workarounds for all the problems we found in GAE, we were starting being fast with the development of features eventually, and at that point we found the cloud was totally unstable, doggy.
Carlos Ble’s post lists 13 issues they’ve had with Google App Engine. Now, I know Google App Engine is not offering the best experience or performance, has a couple of (interesting?) constraints and Google support is (how to put it gently?) completely missing, but some of the points listed in there make me think they’ve thrown themselves in heads first without trying to understand:
- what kind of persistency is Google App Engine offering
- how to model and access your data in Google App Engine
- data migration paths
- architecting with SLAs in mind
These should sound kind of familiar to everyone building distributed systems using NoSQL databases. Going live after prototyping a “Hello world” with a NoSQL database will not gonna “scale” :-).
Original title and link: Goodbye Google App Engine (GAE) (NoSQL databases © myNoSQL)
