4 ms·

Re: deprecation, I deployed a personal project 7 years ago to AppEngine, and it has run continuously since then, costing me a few cents each month above what th

Re: deprecation, I deployed a personal project 7 years ago to AppEngine, and it has run continuously since then, costing me a few cents each month above what the free tier provides. Since then I've redeployed a few times with little bugfixes or features, and all the infrastructure changes together have required a few lines to be removed from config files, and that's it. It still runs exactly as designed, 7 years later. By far one of the best effort/reward ratios I've had on any platform. No OS upgrades, no package version conflicts, no downtime (that I've noticed), just deploy and forget. That said, I'm not sure I'd use it for anything that might scale heavily with datastore writes. They get expensive very quickly if you can't cache and group the writes.

outime 8y ago
Google offers a one-year deprecation policy for a bunch of services, including AppEngine: https://developers.googleblog.com/2012/04/changes-to-deprecation-policies-and-api.html https://developers.googleblog.com/2012/04/changes-to-depreca.... One year is not enough for many enterprise customers. On top of this, there is the not-so-distant issue with the sudden price hike of Google Maps API, which made many companies struggle (in this case especially small ones).
nonplus 8y ago
That's because Google has not updated appengine classic in 7 years...
- sayhello 8y ago
  As an engineer working on App Engine, I can assure you that's not true. We've been changing a lot of infrastructure, adding features, fixing bugs, all without users being affected. I'm personally very excited about the Second Generation Runtimes, which have been worked on in parallel, and run the runtimes unmodified.
  - BareNakedCoder 8y ago
    Hey sayhello, ... is it likely GAE-Std-Py3 will ever get ndb, memcache, etc like we had with GAE-Std-Py27?
- snovv_crash 8y ago
  For Enterprise that can be considered a good thing.
jontro 8y ago
The maste/slave datastore deprecation burnt us. The migration couldn't be staged and when migrating the db locked up. The issue had to be fixed on googles end and caused us a bit of downtime. The engineering resources to migrate was also a problem with the whole stack having needed to be updated.

outime 8y ago

Google offers a one-year deprecation policy for a bunch of services, including AppEngine: https://developers.googleblog.com/2012/04/changes-to-deprecation-policies-and-api.html https://developers.googleblog.com/2012/04/changes-to-depreca.... One year is not enough for many enterprise customers. On top of this, there is the not-so-distant issue with the sudden price hike of Google Maps API, which made many companies struggle (in this case especially small ones).

nonplus 8y ago

That's because Google has not updated appengine classic in 7 years...

sayhello 8y ago
As an engineer working on App Engine, I can assure you that's not true. We've been changing a lot of infrastructure, adding features, fixing bugs, all without users being affected. I'm personally very excited about the Second Generation Runtimes, which have been worked on in parallel, and run the runtimes unmodified.
- BareNakedCoder 8y ago
  Hey sayhello, ... is it likely GAE-Std-Py3 will ever get ndb, memcache, etc like we had with GAE-Std-Py27?
snovv_crash 8y ago
For Enterprise that can be considered a good thing.

jontro 8y ago

The maste/slave datastore deprecation burnt us. The migration couldn't be staged and when migrating the db locked up. The issue had to be fixed on googles end and caused us a bit of downtime. The engineering resources to migrate was also a problem with the whole stack having needed to be updated.