Google App Engine 1.5.0 released

#1

Post by mattrjacobs » Tue, May 10, 2011, 5:45 PM UTC

Google App Engine 1.5.0 released
googleappengine.blogspot.com

Re: Google App Engine 1.5.0 released

#2

Post by timmorgan » Tue, May 10, 2011, 6:08 PM UTC

"We have added a few restrictions to the Mail API to improve the reliability and reputation of the service for all applications. First, emails must be sent from email accounts managed by Google (either Gmail, or a domain signed up for Google Apps). Second, we’ve reduced the number of free recipients per day from 2000 to 100 for newly created applications."

Probably good news for SendGrid.

Re: Google App Engine 1.5.0 released

#3

Post by gte910h » Tue, May 10, 2011, 6:11 PM UTC

The constant instances seem like a bid to take over the heroku type space.

Re: Google App Engine 1.5.0 released

#4

Post by fletchowns » Tue, May 10, 2011, 6:19 PM UTC

gte910h wrote: post #3

The constant instances seem like a bid to take over the heroku type space.

There were a lot of complaints from people that had infrequently used (new) web apps, and so there would be a substantial delay to spin up an instance when the app did get hit. This makes your site seem "slow" even though it really isn't, which is a big problem if you are trying to build some momentum, or show off your site to potential investors. People were resorting to some less than ideal ways for keeping their instances warm, more information on the app engine for java group: http://code.google.com/p/googleappengine/issues/detail?id=24...

Re: Google App Engine 1.5.0 released

#5

Post by gte910h » Tue, May 10, 2011, 6:22 PM UTC

fletchowns wrote: post #4

gte910h wrote: post #3

The constant instances seem like a bid to take over the heroku type space.

There were a lot of complaints from people that had infrequently used (new) web apps, and so there would be a substantial delay to spin up an instance when the app did get hit. This makes your site seem "slow" even though it really isn't, which is a big problem if you are trying to build some momentum, or show off your site to potential investors. People were resorting to some less than ideal ways for keeping their i…

Oh I've used some of the "less than ideal" things during demos before. It truly was an underserved need within the ecosystem.

Re: Google App Engine 1.5.0 released

#6

Post by evangineer » Tue, May 10, 2011, 6:30 PM UTC

gte910h wrote: post #3

The constant instances seem like a bid to take over the heroku type space.

I take it that you're talking about the new Backends:

Backends are special App Engine instances that have no request deadlines, higher memory and CPU limits, and persistent state across requests. They are started automatically by App Engine and can run continously for long periods. Each backend instance has a unique URL to use for requests, and you can load-balance requests across multiple instances.

Re: Google App Engine 1.5.0 released

#7

Post by codesink » Tue, May 10, 2011, 7:32 PM UTC

evangineer wrote: post #6

gte910h wrote: post #3

The constant instances seem like a bid to take over the heroku type space.

I take it that you're talking about the new Backends: Backends are special App Engine instances that have no request deadlines, higher memory and CPU limits, and persistent state across requests. They are started automatically by App Engine and can run continously for long periods. Each backend instance has a unique URL to use for requests, and you can load-balance requests across multiple instances.

Backends seem overpriced to me; their default backend is a long-lasting process running at 1.2Ghz allowed to use 256MB of RAM and it's priced $0.16/hour ($115/month).

They can shutdown/restart/relocate your backend whenever they want so what they suggest to keep your service live is "Configuring more backend instances than are normally required to handle your traffic patterns" (yeah that's at least another $115/month fee).

Re: Google App Engine 1.5.0 released

#8

Post by [deleted] » Tue, May 10, 2011, 7:42 PM UTC

timmorgan wrote: post #2

"We have added a few restrictions to the Mail API to improve the reliability and reputation of the service for all applications. First, emails must be sent from email accounts managed by Google (either Gmail, or a domain signed up for Google Apps). Second, we’ve reduced the number of free recipients per day from 2000 to 100 for newly created applications." Probably good news for SendGrid.

[deleted]

Re: Google App Engine 1.5.0 released

#9

Post by chrisfarms » Tue, May 10, 2011, 7:44 PM UTC

gte910h wrote: post #3

The constant instances seem like a bid to take over the heroku type space.

Backends are not primarily intended for user-facing traffic

I believe they are more like Tasks on Steroids than a way of having something like a little persistant VPS for your app.

Re: Google App Engine 1.5.0 released

#10

Post by timmorgan » Tue, May 10, 2011, 7:48 PM UTC

[deleted] wrote: post #8

timmorgan wrote: post #2

"We have added a few restrictions to the Mail API to improve the reliability and reputation of the service for all applications. First, emails must be sent from email accounts managed by Google (either Gmail, or a domain signed up for Google Apps). Second, we’ve reduced the number of free recipients per day from 2000 to 100 for newly created applications." Probably good news for SendGrid.

[deleted]

Good to know. Thanks for clarifying that.