[1] https://www.bloomberg.com/news/articles/2020-07-07/google-de...
(Google Cloud employee here)
That doesn't help the smaller developers though - you just have to hope that Deutsche Bank wants the same things you do, which is.... unlikely.
Which means they may or may not do a good job of feature prioritization, but it's not always "whatever (big customer) wants."
FWIW, when I worked for a larger GCP customer, they seemed fairly decent at hearing about and addressing concerns. I realize cloud functionality (especially interfaces) is accreted over the years, and can't be delivered all at once.
A contract like Deutsche Bank means dedicated GCP customer engineers, professional service engagements at the highest levels, direct conversations with individual product leaders/managers, roadmaps conveyed to their needs, alphas etc etc.
If it's irrelevant to the Deutsche Bank's of customers, then it's of course fair game to get f'd with.
And the products won't go anywhere.. for Deutsche Bank. This is common for enterprise contracts. It means jack shit for consumers.
Is that really true? I don't have a lot of experience with Firebase, just notifications and analytics, but working with Cognito and Amplify one- two years ago was like a bad joke, more similar to a fledgling startup than a well-rounded offering.
It rather seems to me that a lot of organisations are moving to GCP; BigQuery and its integrations with other Google products seems like a killer app, and GKE is seen as the better choice for hosted Kubernetes.
I'm still a fan of Red Hat's OpenShift, but I'm actually surprised how well Google seems to be managing their {S,P,I}aaS offerings and strategy in this space.
I should have known better though. Like I said, I've been through a lot of Google shutdowns and various screw jobs (remember the Google App Engine price hike?).
AWS is a professional product. It has warts but it's much more solid than GCP, technically and from a business perspective.
† Except search, email and phone.
We updated to working versions, but support kept telling us we were using the old one. Turns out they didnt update the dataflow runtime, which they own and we cant inspect or update, and they were reporting it to us for us to fix...
https://cloud.google.com/network-connectivity/docs/vpn/depre...
Here's a take from an ex-googler:
https://medium.com/@steve.yegge/dear-google-cloud-your-depre...
What, exactly? AWS is legendary for maintaining compatibility. Steve Yegge's article gives a good break down on how infamous GCP's deprecation practices are.
I was lucky in that GCP killed off the feature I wanted before I ever used it, so I didn't have to get burned in production. AWS has never burned me. (GCP used to have a service to do transformations on images in object storage, which I learned about in an App Engine book. It took me a few hours of searching to even find the deprecation notice. Now I just use https://github.com/awslabs/serverless-image-handler because I don't trust GCP).
We can't even be sure whether GCP itself will be around in 3 years:
> In early 2018, top executives at Alphabet debated whether the company should leave the public cloud business, but eventually set a goal of becoming a top-two player by 2023, according to a report from The Information on Tuesday. If the company fails to achieve this goal, some staffers reportedly believe that Alphabet could withdraw from the market completely. [1]
That's disputed and is not hard data, but there's not any positive reason to believe that GCP will exist after 2023 either.
[1] https://www.cnbc.com/2019/12/17/google-reportedly-wants-to-b...
What evidence are you referring to here?
That alone is more than enough to substantiate what I'm saying, but if you need more examples than just search or read HN a bit, due diligence, etc. I was personally lucky in that I got burned in the planning stages and didn't have to get burned in production, but I still wasted all that planning time and ended up having to use AWS instead.
GCP doesn't seem to provide a full list of deprecations, but the list for just one service[1] is pretty terrifying when you consider that your app might depend on two or three dozen services, and a deprecation in just one of them forces you to rewrite perfectly good code. A cursory search reveals a number of reports of being repeatedly bitten by deprecations[2][3][4], so no one should be mislead by the dismissals here. [2] has a good cautionary tale of a forced "upgrade" leading to potentially much greater cost.
[1] https://cloud.google.com/appengine/docs/deprecations [2] https://nilsnh.no/2019/11/09/managing-the-google-cloud-platf... [3] https://www.slideshare.net/async_io/lessons-learned-from-bui... [4] https://www.lastweekinaws.com/podcast/aws-morning-brief/whit...
I do think Google Cloud is trying to do better and the few deprecations I’ve seen personally have been heavily scrutinized and considered, with a clear migration path for users. I was only asking for data to objectively understand the problem as it stands today, and not to minimize your own experience. I know there are experiences similar to yours, but hopefully there are far fewer in recent years (but its always hard to tell without data).
There seems to be a general fear about Google potentially killing off a product, based on recent history [1]. Now I know most of these are on the consumer side of things, but you can imagine people's concerns if the same thing started happening to Google Cloud products. Is the GCP team aware of these concerns, (or is this just a HN crowd concern) and if so, are there steps being taken to address this perception head on?
[1] https://killedbygoogle.com/