News for hackers. Stuff that matters.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by Top19 on Thursday December 07, 2017 @11:36AM (#15871491)
It’s actually double lock-in, so 2x worse.

You used to have to just be afraid of lock-in, which I don’t think is as big an issue as it sometimes seems.

But with Google, you’re not only locked in but might be LOCKED OUT when they kill your product.

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by chatmasta on Thursday December 07, 2017 @11:51AM (#15871624)
Don’t be ridiculous. Google killing a feed reader is a way different from Google killing a cloud service with paying customers and SLA agreements.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by un_montagnard on Thursday December 07, 2017 @11:52AM (#15871634)
Like the QPX Express API?
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by chatmasta on Thursday December 07, 2017 @11:55AM (#15871668)
Interesting point. However that’s not a google cloud product and never had an SLA (the QBX FAQ says “we do not guarantee support”). It’s also a unique case because of its reliance on third party data vendors.

If google starts killing their cloud products, I will eat my socks. Just let me wash them first.

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by nik736 on Thursday December 07, 2017 @11:55AM (#15871663)
?? This happened before.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by non_sequitur on Thursday December 07, 2017 @11:58AM (#15871692)
This is from their legal agreement:

7.1 Discontinuance of Services. Subject to Section 7.2, Google may discontinue any Services or any portion or feature for any reason at any time without liability to Customer.

7.2 Deprecation Policy. Google will announce if it intends to discontinue or make backwards incompatible changes to the Services specified at the URL in the next sentence. Google will use commercially reasonable efforts to continue to operate those Services versions and features identified at https://cloud.google.com/terms/deprecation without these changes for at least one year after that announcement, unless (as Google determines in its reasonable good faith judgment)

So technically they can do it, though their enterprise customers likely have stronger agreements that require at least X time (probably 1 year) notice

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by chatmasta on Thursday December 07, 2017 @12:03PM (#15871728)
Of course they can do it. I’m sure similar language exists in AWS and Azure agreements.

Look, I hate a lot of what Google stands for and where it’s going. But I find it very implausible they’ll kill any non-beta products that are part of google cloud platform. GCP is poised to take the place of AdWords as the google golden goose, helping them to diversify from their heavy reliance on advertising for revenue. They do not want to screw that up.

I’m sure they are well aware of the uprising that would cause amongst developers, aka the core customers of GCP. It would be a stupid move in a highly competitive cloud market, effectively telegraphing the fact that you can not rely on GCP services to exist in perpetuity. Their competitors would likely respond by re-implementing the shut down product with a compatible API so they could literally steal disgruntled users from GCP.

If you’re really concerned about this, the solution is pretty simple: don’t use GCP. If you want to use it, then only rely on the very core services that google clearly has strong incentives not to kill. Those would likely be VMs and any products that have an equivalent at another cloud vendor.

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by jacksmith21006 on Thursday December 07, 2017 @12:09PM (#15871770)
Silly statement. Google is in the cloud business and this is very different than a free product they offer.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by kuschku on Thursday December 07, 2017 @12:50PM (#15872214)
The Flights API they just killed? Custom searches, which many websites paid for, which they killed?

Google has a habit of killing things, no matter if you pay for it and your business relies on it, or not.

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by jedmeyers on Thursday December 07, 2017 @01:34PM (#15872665)
If I remember correctly, they were required to keep that API up for a specified amount of time after the acquisition and they have kept it longer than that.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by kuschku on Thursday December 07, 2017 @02:40PM (#15873295)
And that’s an excuse how?

Many of their cloud APIs are also acquisitions. The entire Firebase product line, and the Fabric.io product line are acquisitions.

Should we expect those to also disappear suddenly?

Re:Moving the NYT Games Platform to Google Cloud With Zero D... by panopticon on Thursday December 07, 2017 @05:04PM (#15874798)
I think the difference is that the QPX was the byproduct of an acquisition (ITA Software) while Firebase and Fabric.io were the desired targets in those respective acquisitions.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by jedberg on Thursday December 07, 2017 @01:04PM (#15872388)
Usually when a large company relies heavily on a cloud provider, they have an additional contract that specifies, among other things, advanced warning of any pending shutdown, often measured in years, to give them enough time to adjust and also to appease their shareholders and auditors.
Re:Moving the NYT Games Platform to Google Cloud With Zero D... by eitally on Friday December 08, 2017 @01:01AM (#15876969)
And even without this, Google has a history of proactively notifying paying customers years in advance of termination of a commercial enterprise service. The Search Appliances are a perfect example -- EOL was announced a couple years ago but support has persisted for existing customers and only next spring will they finally be fully unsupported. Moreover, Google is actively offering migration plans & assistance to move GSA customers to the new Cloud Search service, or even to third party indexers like Elastic.

I get the gist of the OP's complaint, but like you said, that behavior pattern is just not tenable in the kind of operating environment Google Cloud finds itself in these days.

Disclaimer: I work for Google Cloud, but not on any of the aforementioned products.