 |
| App Engine engineers talk to developers in the cloud platform sandbox at Google I/O |
- In our overview session, Peter Magnusson and Greg D’Alesandre introduced many of our new features and announced that we have attained 7.5 billion hits per day and are running more than 1 million active applications.
- We announced Google Compute Engine and Alon Levi and Adam Eijdenberg showed how to use App Engine to orchestrate compute instances.
- Cloud SQL began taking open signups and we witnessed an epic battle of the backends in our SQL vs NoSQL session, with Alfred Fuller representing the Datastore and Ken Ashcraft representing Cloud SQL.
- We announced Google Cloud Endpoints and hosted a codelab to give developers early access to our trusted tester program.
- Brian Quinlan covered the finer points of the Python 2.7 runtime.
- And last but not least, Marzia Niccolai, Greg Darke and Troy Trimble gave some great tips for optimizing App Engine applications.
We’ll be taking a short break from our regularly scheduled release cycle in July, but we’ll get back on our usual drumbeat of monthly releases in August.
- Posted by the Google App Engine Team
5 comments:
Could someone put up the video for optimizing app engine applications.
can someone fix google app engine ? Our java apps are constantly going offline for hours ( stop responding and finally throw 500 internal error ) . At least open source the core platform layer so we can fix the issues by ourselves. It really doesn't make sense to add new features if you can't maintain a stable, production ready set of features.
@Mihai
It works perfectly for us, serving 5-10M requests per day. You must be doing something wrong.
I'm wondering why it works just fine for several days and suddenly it stops working / responding properly even if we are not changing any config or nor add new data. I think it's a platform issue as known as DeadlineExceededException.
Just googleing it I see I'm not the only one.
Here is the log http://pastebin.com/eZN0vaVT
btw : what kind of framework/technology stack are you using (i.e. spring MVC ) ?
It works perfectly for us, serving 5-10M requests per day. You must be doing something wrong.Thanks
Post a Comment