Hacker News Reader

Comment by dragonwriter | Hacker News Reader

> I think the point is though that if there is even a chance that a service will be shut down in a year then even on a financial basis, the cost savings up to that point will be drowned out by the switching cost.

There is always a chance that a service will be shut down in a year no matter who the provider is.

View on HN

And when that chance is perceived to be particularly high at Google people will act accordingly.

Even if you think it's equal, we're probably in a regime of "nobody got fired for building on AWS".

AWS DevOps here (besides my many other jobs titles/responsibilities).

When was the last time AWS EOL'd a service? Honestly, I can't remember, and I've been using AWS (S3/EC2 to start) since 2007.

GAE, storage, etc could be close to free, and I'll still stick with Amazon; I'm paying for consistency and the long-term lifecycle of AWS as a system.

> When was the last time AWS EOL'd a service?

When was the last time Google Cloud Platform EOL'd a service? I mean, if you are asking about AWS and not Amazon, you should ask about Google Cloud Platform, and not Google.

Amazon has deprecated & disabled old API versions, SOAP & security issues and the like. I think they removed some of the old SimpleDB eventually consistent Query calls & made strongly consistent Select. Some of the regional API implementation around S3 and the original "us-standard" region were changed. But yeah, AWS has never turned off a service or major feature that I canrecall.

Reply on news.ycombinator.com