Thanks for clarifying this! I am especially relieved to see the
datastore import/export and the billing option announced. I am also
relieved to see recent advances like the HTTPS release which now lets
us add things like Google Checkout integration. As someone who runs
their entire business (http://www.wolfire.com
) on Google App Engine,
here are a few things that I would like to see, for what it's worth:
- The latency for using your own domain. The appspot url is
distributed around the world and extremely fast. We're talking 2 -
8ms in the bay area. However, once you put your app on your own
domain, that latency goes to ~100 ms to 200ms in the bay area. Still
"decent", but slower than what a typical web host would provide. I
would be interested to hear what Google is planning to do about this.
Here is the ticket: http://code.google.com/p/googleappengine/issues/detail?id=531
For what it's worth, the reason I signed up for this service in the
first place is because I was so impressed with the CDN aspect of the
service and the low latency around the world of my pages. I don't
want to tell you guys about your own business, but IMHO, this CDN
aspect of GAE is one of the few things that makes Google unique from
other web hosting providers and Google is one of the few companies out
there that has the necessary infrastructure to pull it off. It's a
shame that GAE isn't reaching its full potential in this regard.
From what I hear, it's internal bureaucracy with the Google Apps team
handling the DNS routing and the GAE handling the other aspect of the
service, but whatever it is, I am sure you guys can solve it.
It's just really frustrating because when I was initially testing it
, the site is so fast, it is literally
instantaneous. Like you click the link, and it is already there.
Even people who aren't tech savvy would comment independently on how
it was the fastest site they had ever seen, but now wolfire.com
actually slower than it was on our original dedicated server.
- Support for naked domains. It's annoying that I have to redirect
people who go to wolfire.com
. If anything, I'd
rather do it the other way around. This also adds to the latency,
ruining our chance for an instantaneous load like on appspot.
- Some fixes for small misc bugs and "features". For example, it is
impossible to set a display name on emails. This is a simple best
practice to make your email look like it was from "Wolfire Games"
rather than jef...@gmail.com
Another example is how GAE doesn't let you set cookies on a 301
I am sure these are tiny bugs that could be corrected in less than a
day of an engineer's work yet they are actually quite important to GAE
users (despite the small number of stars). Basically, I would like a
little more transparency on what the GAE is doing. It would be cool
to maybe allocate a week to just fix all of the low hanging fruit bugs
like these ones rather than spending months working on adding Java
support or HTTPS support exclusively. I can't really comment on what
Google is doing, because I simply don't know, but that is what it
feels like to me.
A few other things to throw out there; a task queue so we can get rid
of the third party server regular http ping hack and full text search.
Sorry if this post sounds negative. I love GAE and don't regret
choosing it as my platform for a minute, but that's my feedback as
someone who works with it every day. :)
On Oct 23, 5:45 pm, "Marzia Niccolai" <ma...@google.com
> Many of you have expressed interest in learning about what's coming next for
> Google App Engine, and although we've often talked about features we plan on
> supporting, we've decided to publish a