Hacker News new | past | comments | ask | show | jobs | submit login

Hey folks - App Engine actually has an explicit deprecation policy spelled out to make sure this can't happen. See https://developers.google.com/appengine/terms



As a recovering hardcore Joke Engine user, I suggest not getting too tied up on TOS minutia as arguments against App Engine when there are plenty technical reasons to avoid it like the plague, e.g.:

- Behavioural changes as a result of unannounced internal release process. Go to bed, wake in morning to app serving 500s (happened twice)

- Design flaw that ran so deep they had to redesign the datastore, insisting on people start migrating before they even had migration tools ready. Prior to that, at least one outage event required running the Google equivalent of fsck and leaving "/lost+found" folders in everyone's datastore (WTF?!?!? Not even once, dude!)

- Latency that varies according to the phase of the moon, and you're billed for it anyway.

- Continually changing architectural story around apps. Last year: Memcache is cheap, free, and shared! This year: Dedicated memcache, only $66/gb/month! 2 years ago: elasticly spun up processes! Last year: dedicated hardware thread, only $100/thread/month!

- Let's not forget the wild pricing changes depending on how much the App Engine team had packed in their crackpipes the night before

- Service characteristics you won't see on any other platform (e.g. DB query latency). So regardless of abstraction layers, your app inevitably ends up designed for a single platform

It's a platform that succeeds only at exposing users with RAM-sized datasets to planetary scale problems, all the while charged handsomely for the privilege of the self-delusion that some edge was gained through all the suffering. Seriously fuck all that. I could turn this into an essay but why bother.


No kidding, the service should be renamed GA2EE. It's slow as hell, never works, and requires you to custom code for their 'enteprise' platform to solve problems no one even has.

God forbid the bill you'd get for actually scaling to a size that started to require whatever GA2EE really is.


To emphasize your point, look at the downtime some Python users experienced just today (this is a link to the official App Engine Google Groups): https://groups.google.com/d/msg/google-appengine/iRb3wrV8AB0...


My company hosts our app on GAE and I could not agree more with this. GAE is horrible. We are paying close to $1000/month and we could get better performance on a $5 Digital Ocean instance. $700 of that is "premier" support which is a joke. We're lucky just to get a response back. Not to mention they broke Python's debugger(PDB) a while back and it took them three month's to fix it.


Leaving GAE is the best thing I ever did.


It clearly says they can do anything they want, but must give you 90 days of warning.


Actually, the policy is:

"Google will announce if we intend to discontinue or make backwards incompatible changes to this API or Service. We will use commercially reasonable efforts to continue to operate that Service without these changes until the later of: (i) one year after the announcement or (ii) April 20, 2015"

So you have a year, at a minimum.


Thanks for that. I stopped reading at:

"Unless otherwise noted by Google, material changes to the Agreement will become effective 90 days after they are posted, except if the changes apply to new functionality in which case they will be effective immediately. If Customer does not agree to the revised Agreement, please stop using the Service."


Yeah, and in those 90 days if things break, they may not work as hard to get it back online, as they would have if there wasn't a deprecation.


They would have to be suicidal to shutter appengine and only give 90 days notice. Won't happen.


"Suicidal"? Realistically what would happen, do you think? They shut down Google Reader, which is probably used by 1000+ times as many people. The average user of Google Apps Engine apps probably has no idea where the service is hosted and will never understand why they should blame downtime on Google.


Comparing this to Google Reader is ridiculous. Google Reader was free, and it had a small potential market. Even if Google Reader had 100% of the market (which I'm sure people will say it did), the number of potential users was not huge, and the amount of revenue they could bring in was pretty small.

Even if App Engine isn't tremendously valuable now, it's a growth market, and easily monetizable. Google isn't going to burn a bunch of customers who could be - if they end up being the next Netflix - worth hundreds of thousands of dollars in recurring revenue.

I wish people would stop with the hyperbolic Google Reader stuff. Google's bread and butter are web ads, and they're a shrinking market. As Facebook can attest, mobile is hard to monetize, and it makes a lot of sense to focus on areas where people can just pay you directly. AWS has already validated this market, Google has the capacity to deliver, they've just fumbled the execution wildly.


I bring it up because Reader was a product that nobody expected to ever go away, until it did.


If you didn't expect a product that had wallowed in practical obscurity for several years with no updates (and no team working on it) to go away then you are a bit silly.


Totally agree on this. Reader was a free software. They may not be making billions out of App Engine but a lot of fortunate 500 are moving to this kind of platform and Google has probably invested tens of billions and thousands of engineers into GAE. No way they will kill this in the next 10 years unless market crashed.

That kind of cynical thought should be eliminated.


>They may not be making billions out of App Engine but a lot of fortunate 500 are moving to this kind of platform

Not that many.

>and Google has probably invested tens of billions and thousands of engineers into GAE

If we're speculating, I'd say, far far less.

Except for the parts they use themselves too, anyway.


But reader was not used by 1000+ times as many people, quite the opposite. They namedropped vice which itself has far more daily readers than Google reader had. That's one customer, there are thousands of others that use app engine to serve billions of page views a day.

Stop wallowing over reader and move on.


That doesn't mean much. When google deprecates something, it might as well already be shut off. http://techcrunch.com/2012/09/24/feedburner-experiencing-sta...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: