Supposedly the funding for Google Cloud will go bye-bye if they don't beat Azure by 2023. They won't axe all of Google Cloud, but I bet they'll start killing services that don't make money. (Remember: Google is an advertising company; loss-leading cloud services don't help them sell ads)
nah the article was really overblown. 'we've approved budget for five years. and our goal is to beat azure.' more or less, but that doesnt mean in five years there wouldn't be more budget approved, and it didnt seem like an ultimatum connecting the two. businesses dont plan infinite years out.
while google cloud as a whole i dont see going away, individual products within it(like iot core) are gonna always be up for the chopping block
The article is overblown but the point remains: if GCP doesn't stop shedding money, the business is not going to let it burn cash indefinitely on a fool's errand. There will be pull-back and we don't know what services (or regions) will be affected. This may be the first of a trend.
"Google Cloud still operating at a loss despite revenue, client wins" (https://www.ciodive.com/news/google-cloud-revenue-Q2-2022/62...). Their revenue increased but so did their losses by about the same percentage. They are still 14% behind Microsoft's marketshare. They are leaning into a niche of "data, analytics, security", which is so broad that it won't take much for their competitors with much larger market share to eat their lunch.
A year ago they said they'd be profitable by this time. A year before that they said the same thing.
It's kind of sad. All that technology and nobody wants them, like a nerd without a date.
That's why I prefer to invest time and effort on AWS. I know I won't have to rewrite everything from scratch whenever Google feels like abandoning their projects.
To the best of my knowledge, no. At least none of the AWS services I've used. They've deprecated support for some CAs and stuff, but that seems reasonable.
There have been rare changes, like mandatory API version upgrades or some features being turned off. I do not recall anything being removed without a (better) replacement available beforehand, let alone entire simply services being turned off. See simpleDB as the canonical example of long term deprecation but continued availability.
Disclosure: long time Principal at AWS. The above is my own observation and opinion
Not that I'm aware of. They'd be fully justified in shutting down simpleDB since it hasn't had a feature update in over a decade, but they still keep it running. New accounts can't sign up for it and it only exists in the oldest regions.
They were going to retire old s3 path styles, but they changed their mind after customer feedback.
That's exactly what you will do - invest time, and energy, a lot of both because AWS is a victim of its own legacy. Everything is an after-thought, everything is messy and its genuinely painful to use on anything except some basic UI driven functionality.
EC2 and S3 and some basic hosting stuff is fine but newer services such as AWS Glue, Athena etc are a horrendous mess for anything other than 101 type stuff.
EC2-Classic was not its own service. It was a specific configuration of EC2. They retired that configuration by providing a full migration path into a new system that could be configured to perfectly replicate the old system if you wanted it to. Having gone through that migration myself with a bunch of services a long time ago, this isn't really a good example of a thing that AWS has killed off.