We use it at bynd.com for a bunch of projects; we've deployed at least 30 applications on it now. It has taken me quite a while to get used to the AE way, and I

We use it at bynd.com for a bunch of projects; we've deployed at least 30 applications on it now. It has taken me quite a while to get used to the AE way, and I don't love it, but it is very good for some things. I can think of lots or pros and cons, but off the top of my head: Pros: - scaling is amazing; we've had sites go from 1 to over 1000 instances in a few minutes; from <1 to 1600 queries per second in the same time. - reliability is pretty good now - if you let go of the idea of doing everything synchronously life gets a lot easier, and deferred processing is really easy to do. - the development process is great: download SDK, checkout code, point SDK at code and you're off. Then you develop locally and have it run exactly the same (with a handful of caveats) as it does appspot. It's a really low barrier to entry. Cons: - webapp (the default framework) sucks. Once you find something like tipfy, webapp2, or flask life gets a lot better - changing your datastore structure can really suck with a live site. There's still no simple way of getting data on and off, or of doing backups. Messing with your live database if you need to fix some bug can be scary - it takes some time to grok the right way to model data, and to use the datastore. - there's a lot of "here's how to get started / build a simple blog" info, very little on best practices, how to model complex data, how to do maintenance...