Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud Prediction API End of Life

cloud.google.com

Post reply on HN
Print view View original

31–40 of 124 posts

Re: Google Cloud Prediction API End of Life

#31

Post by yeukhon »

decwakeboarder wrote: post #28
yeukhon wrote: post #26

Earlier quoted context omitted.

I believe they aren't allowed to change the hardware spec, so at some point they will not be able to get supplies anymore. As far as SimpleDB, yeah, believe it or not, on AWS bill, it still exist and most support engineers from Amazon don't really have a clue why it's there. I still don't know which service we use is using SimpleDB. Only a few cents, so nobody really care.

Is that true? They'd still need to adhere to HVM vs. PVM, but that should be it.

Well, they advertised m1 as such and such hardware spec. I don't know if in their ToS they state they would be allowed to change the spec without notifying customer. Maybe.

I believe m1 is only available on PV.

Re: Google Cloud Prediction API End of Life

#32

Post by NetMonkey »

powera wrote: post #22
aibottle wrote: post #11

Earlier quoted context omitted.

Doesn't matter. To general masses it just looks (and well you will have to change code) like they shut down another thing after short time people relied on. Bad move Google. Just stop offering it and keep in running in quiet for people who have it next time.

The general masses neither know nor care about this API. "Business" folks will see they have a year to transition to an improved version of the product.

Business folks: So instead of new features we have sold to customers we have to spend X weeks on this feature which was working perfectly fine?

Re: Google Cloud Prediction API End of Life

#33

Post by endymi0n »

hackunomatter wrote: post #20
resoluteteeth wrote: post #12

Earlier quoted context omitted.

It still might not be a great idea for Google to routinely shut down APIs in favor of other APIs if they want people to actually rely on its cloud services. It doesn't look like Google is interested in trying to make the migration particularly easy either: > Q: What will happen with my existing models? > A: You must recreate your existing Prediction API models using Cloud Machine Learning Engine. To learn more, pleas…

They _are_ giving a 1 year notice.

This. In GCP, they are handling these things transparently, professionally and proactively - usually giving you a personalized heads-up, alternatives and reminders as early as possible. Facebook on the other hand has been shutting down critical APIs under my systeme literally with a days' notice.

Re: Google Cloud Prediction API End of Life

#34

Post by tuna-piano »

soccerdave wrote: post #4

One thing that I find so amazing about AWS (Amazon Web Services) is that I'm not aware of them ever EOLing one of their apis (I could be wrong). We still have a bunch of code that still uses SimpleDB and even though they haven't promoted SDB for a while, they haven't EOLed it.

Exactly this. Companies are still running on-prem software from decades ago, because it's not economical to migrate. Why should the cloud be different?

It's very scary to a purchasing manager at a company to know that when they invest $100k+ in developer/consultant time implementing a solution, that every 3-5 years they will need to spend an additional $xk to simply keep the solution alive!

AWS is doing this right. I can't imagine recommending Google for many cloud use cases, given their propensity to decommission software that companies use!

Re: Google Cloud Prediction API End of Life

#37

Post by skybrian »

themihai wrote: post #23
vgt wrote: post #5

Before folks start comparing this to Reader or point to the general "Google shuts things down" narrative, Prediction API has been superset by the array of ML APIs and Google Cloud ML, found at [0]. [0] https://cloud.google.com/products/machine-learning/ (work at G)

yeah, and we should all be happy when we are forced to migrate to new APIs...like the old APIs got rust. This's one of the reasons why proprietary "cloud" services are so bad. Once they are gone you have little or no choice. Nobody would complain much if Google would shut down its MySQL "cloud" service. Amazon is just there and if Amazon doesn't fit the bill you can use a old good metal server. Not the same you can s…

Tensorflow is open source and apparently very popular, so I'm guessing this migration would be moving in the direction of less lock-in.

Re: Google Cloud Prediction API End of Life

#38

Post by mysterydip »

vgt wrote: post #5

Before folks start comparing this to Reader or point to the general "Google shuts things down" narrative, Prediction API has been superset by the array of ML APIs and Google Cloud ML, found at [0]. [0] https://cloud.google.com/products/machine-learning/ (work at G)

How much of the API is the same? Would the average project require a 5%, 50%, etc rewrite?

Re: Google Cloud Prediction API End of Life

#39

Post by skybrian »

NetMonkey wrote: post #32
powera wrote: post #22

Earlier quoted context omitted.

The general masses neither know nor care about this API. "Business" folks will see they have a year to transition to an improved version of the product.

Business folks: So instead of new features we have sold to customers we have to spend X weeks on this feature which was working perfectly fine?

Since nobody here has yet admitted to using this API, these business folks are rather hypothetical so far.

(I expect some exist, but we haven't heard from them yet.)

Re: Google Cloud Prediction API End of Life

#40

Post by BinaryIdiot »

theDoug wrote: post #30
omarforgotpwd wrote: post #24

"Let's build our entire stack around Google Cloud. I'm sure they won't shut down an API we depend on"

This one-year-long deprecation warning comes atop what is a fairly reasonable migration path for most users. I have yet to hear of a single user of any size whose “entire stack” relied on a single API, let alone this one, and who would be left without a faster, easier, or less expensive option in this move. But you might have info I do not! (Work at Google Cloud)

> This one-year-long deprecation warning comes atop what is a fairly reasonable migration path for most users

After working at multiple, large companies as well as doing government contracting, it would take a year just to propose and get funding for very minor changes. Sometimes it would take months to get critical bugs or security issues approved and taken care of.

A year works for many tech companies. Maybe even most. But it's laughably tone deaf when talking about larger companies or government organizations.

This is why the majority of companies I've worked with opt for APIs from, say, AWS and only consider using a Google API if there is literally no other choice. No one wants to be focused on X and suddenly have to allocate money to change something that's working to use something else.

Post reply on HN