Appengine is great for some things, and not so great for others. If you have a Twitter-level service, you are going to be better off running it on your own optimised platform, end of story. If you have the royal wedding website to host, Appengine is great because you pay for those few days and no more.
It's also great for most developer-centric startups. you can get your service up and running without the considerable expense of hiring good sysadmins. If you don't hit the big time, you'll pay almost nothing. If you do, it'll handle it until you have the resources to hire those sysadmins to build you that optimised platform. I don't understand why everyone expects Appengine to be the perfect platform for every possible application. If vijayp feels Partychat is better on AWS, good for him. Although I do hope he's got the app distributed over more than one domain though, to prevent the day-long outages they've had in the last six months. Personally I've chosen appengine so I don't have to even think about such issues, but that's because I'm more interested in developing apps than architecting scalable and highly available systems. YMMV. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
