Google App Engine turns 2
googleappengine.blogspot.com
Google App Engine turns 2
1–10 of 27 posts
Re: Google App Engine turns 2
#2Until they speed up the datastore by a factor of 10 the app engine just isn't a viable platform. They don't even use it internally for that very reason (this is coming from colleagues who work there.)
Re: Google App Engine turns 2
#3Apart from being the tipping point - nudging me to start out on my own with its liberal free quotas, I should also thank Google App Engine for not supporting Java during the initial release and thus exposing me to Python.
Coming from corporate Java and RDBMS world, the non-RDBMS datastore (BigTable), Python and having to scale while being more resource conscious, have all been pleasant experiences.
Re: Google App Engine turns 2
#4Until they speed up the datastore by a factor of 10 the app engine just isn't a viable platform. They don't even use it internally for that very reason (this is coming from colleagues who work there.)
How do you reconcile that statement with the fact that tons of developers do actually use it? Myself included. ;)
Re: Google App Engine turns 2
#5As you begin your 3rd year, here are a few things I wish for you:
1. May you be able to work with your brother, Google Apps, to allow SSL support for custom domains.
2. May you be able to lift your 1 MB cap per urlfetch request to at least 10 MB so that your users can write some cool apps using the YouTube API.
3. May you inherit some snazzy search skills this year from Google Search, your grand daddy, and allow your users to whip up custom search engines for their apps in the blink of an eye (or the press of a button, rather).
Happy Birthday GAE!
- All of your 250k users.
Re: Google App Engine turns 2
#6Until they speed up the datastore by a factor of 10 the app engine just isn't a viable platform. They don't even use it internally for that very reason (this is coming from colleagues who work there.)
How do you reconcile that statement with the fact that tons of developers do actually use it? Myself included. ;)
What do the error rates on write operations look like these days?
This ticket has held me back from giving appengine a try so far: http://code.google.com/p/googleappengine/issues/detail?id=76...
Re: Google App Engine turns 2
#7Until they speed up the datastore by a factor of 10 the app engine just isn't a viable platform. They don't even use it internally for that very reason (this is coming from colleagues who work there.)
How do you reconcile that statement with the fact that tons of developers do actually use it? Myself included. ;)
We use it too. That's why I can make that statement.
A DB request takes over 100ms on the datastore. That's insane and unusable for about 90% of applications. Even their implementation of memcached is several orders of magnitude slower than actual memcached.
Re: Google App Engine turns 2
#8Earlier quoted context omitted.
How do you reconcile that statement with the fact that tons of developers do actually use it? Myself included. ;)
What do the error rates on write operations look like these days? This ticket has held me back from giving appengine a try so far: http://code.google.com/p/googleappengine/issues/detail?id=76...
This was largely solved in 1.3.1. I quote:
Reduced error rate with Automatic Datastore Retries - We've heard a lot of feedback that you don't want to deal with the Datastore's sporadic errors. In response, App Engine now automatically retries all datastore calls (with the exception of transaction commits) when your applications encounters a datastore error caused by being unable to reach Bigtable. Datastore retries automatically builds in what many of you have been doing in your code already, and our tests have shown it drastically reduces the number of errors your application experiences (by up to 3-4x error reduction for puts, 10-30x for gets).
Re: Google App Engine turns 2
#9As you begin your 3rd year, here are a few things I wish for you: 1. May you be able to work with your brother, Google Apps, to allow SSL support for custom domains. 2. May you be able to lift your 1 MB cap per urlfetch request to at least 10 MB so that your users can write some cool apps using the YouTube API. 3. May you inherit some snazzy search skills this year from Google Search, your grand daddy, and allow your…
Top two are in the roadmap http://code.google.com/appengine/docs/roadmap.html
Re: Google App Engine turns 2
#10As you begin your 3rd year, here are a few things I wish for you: 1. May you be able to work with your brother, Google Apps, to allow SSL support for custom domains. 2. May you be able to lift your 1 MB cap per urlfetch request to at least 10 MB so that your users can write some cool apps using the YouTube API. 3. May you inherit some snazzy search skills this year from Google Search, your grand daddy, and allow your…
The first one is a non-starter for many startups.