I have sticked on AppEngine for 2 years but I found that most of the points in the article are valid.
AppEngine is great in general but the datastore is really disappointed which leads to many problems in reality. Especially after the Sept's maintenance which my app is still having around 1%-2% of DB timeout ever since. On Nov 23, 10:17 am, nischalshetty <[email protected]> wrote: > I built my first twitter apphttp://justunfollow.comon GAE/J. It's > used by a good number of twitter users and I have to say, as a single > developer, if I've been able to manage the app, it has been completely > due to Appengine. I have stopped worrying about the so called "back- > end" and get to concentrate just on the code part of it. > > I've recommended appegine to everyone I know who wanted to build an > app. I'm building my next app on the appengine as well. Though > appengine has had problems, look at their progress. It has been > Upwards which is what gives me hope that the team is on to building > and making things better everyday. > > -N > > On Nov 23, 12:58 am, "Ikai Lan (Google)" <[email protected]> > wrote: > > > > > Hey everyone, > > > Thanks for the support. Yes, SSL for custom domains is on the roadmap: > > >http://code.google.com/appengine/docs/roadmap.html > > > I personally agree the most with Phillippe. Build something awesome, > > build a business on App Engine, or just do something amazing. Let us > > know and we'll do our best to feature your business when we talk about > > App Engine. > > > In parallel to all the cool features coming out (have you guys *seen* > > the 1.4.0 release notes?), we're working on a ton of projects to > > address reliability concerns across the board. This is a product > > that's always growing and always improving. > > > -- > > Ikai Lan > > Developer Programs Engineer, Google App Engine > > Blogger: http://googleappengine.blogspot.com > > Reddit: http://www.reddit.com/r/appengine > > Twitter: http://twitter.com/app_engine > > > On Mon, Nov 22, 2010 at 11:35 AM, Philippe Beaudoin > > > <[email protected]> wrote: > > >> The best defense is not a rebuttal of negative things written about > > >> App Engine. The best defense is an active and visible ecosystem. App > > >> Engine does have that. > > > >> What could we do to improve it and publicize it more? > > > > +1 > > > > Don't spend time on flame wars. Go out and do something. :) > > > > AppEngine Java is working very well for us. Sure, we run into problems > > > once in a while, but nothing that has proved overly hard to solve. And > > > having the platform maintained by Google is proving very valuable to > > > us, it seriously cuts down on maintenance cost. We do full text search > > > and it's not a "hack". We do URLFetch and don't run into the problems > > > mentioned there. The key has been to learn the platform first and > > > write with its limitation in mind. (And most of them I don't see so > > > much as "limitations", but rather as "good practices" that will allow > > > you to develop a scalable application.) You can see our app there: > > > http://corp.bookedin.net/ > > > > Cheers, > > > > Philippe > > > > -- > > > 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 > > > athttp://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.
