News for hackers. Stuff that matters.
Re:How Figma's databases team lived to tell the scale by umvi on Thursday March 14, 2024 @02:28PM (#39707350)
Never a good idea to rely on Google proprietary tech (unless you are Google)... it could be sunset at any time without warning. I use GCP but I try my best to stay Google agnostic (avoid GCP-only offerings, etc) so that I can move to AWS if Google pulls the rug out from under me.
Re:How Figma's databases team lived to tell the scale by weitendorf on Thursday March 14, 2024 @04:13PM (#39708445)
I'm biased having worked on GCP, but I think GCP actually has a very good track record of not sunsetting entire products or removing core functionality. When I worked on AppEngine, I would often see apps written 10+ years ago still chugging along.

It is true though that GCP sometimes sunsets specific product functionality, requiring changes on the customers' part. Some of these are unavoidable (eg committing to apply security patches to Python 2.7 given that the rest of the world is mostly not upstreaming these patches anymore), but not all of them.

I would certainly use Cloud Spanner externally now that I've left the company, and IMO spanner has such a compelling featureset that it's a strong reason to use GCP for greenfield development. The problem though is that it's only available on GCP, and could become expensive at large scale.

Re:How Figma's databases team lived to tell the scale by jerrygenser on Thursday March 14, 2024 @05:33PM (#39709235)
>It is true though that GCP sometimes sunsets specific product functionality, requiring changes on the customers' part. Some of these are unavoidable (eg committing to apply security patches to Python 2.7 given that the rest of the world is mostly not upstreaming these patches anymore), but not all of them.

A good example is probably IoT. I've heard first hand anecdotes of very difficult migrations off this service.

Re:How Figma's databases team lived to tell the scale by nojvek on Thursday March 14, 2024 @08:52PM (#39710908)
My previous employer was a GCP customer. Google did pull occasional shenanigans totally breaking us with random upgrades without notifying us. Their support wouldn’t acknowledge it was their fault until we were mad at them.

My newer employer is AWS. Their offerings are a lot more stable and support is helpful.

If you want to build a serious business I would avoid GCP. Google doesn’t really give a shit at winning Cloud. Ads is their core business.

Re:How Figma's databases team lived to tell the scale by weitendorf on Thursday March 14, 2024 @10:11PM (#39711389)
Ugh I'm so sorry, you should definitely have been notified in advance about breaking changes, unless they were accidental bugs and regressions. That was something we took pretty seriously for the products I worked on.

I have definitely enjoyed using AWS support. But I've also encountered some broken/janky functionality (eg using custom domain + api gateway + websockets + Lambda for the apparently niche-task of having a real website use the Lambda-websockets integration) on AWS that I don't think would have made it to production at Google. I also really dislike how they handle project-level logging compared to how it's done on GCP.

Ultimately I do think some GCP products like Bigquery, Cloud Run (I'm biased here), and Spanner as well as general DevEx/reliability factors are compelling enough for GCP to be worth serious consideration, even if AWS offers better support.

Re:How Figma's databases team lived to tell the scale by rockostrich on Thursday March 14, 2024 @03:26PM (#39707960)
GCP products have a much better track record than Google consumer products when it comes to support since there are usually enterprise customers with multi-year contracts worth tens, if not hundreds, of millions of dollars using them.
Re:How Figma's databases team lived to tell the scale by callalex on Thursday March 14, 2024 @03:50PM (#39708223)
That’s what AppEngine customers thought.
Re:How Figma's databases team lived to tell the scale by weitendorf on Thursday March 14, 2024 @03:57PM (#39708293)
I worked on AppEngine (well, Serverless Compute) at Google for over 4 years and left on Friday. Did something happen to AppEngine in the last week?
Re:How Figma's databases team lived to tell the scale by callalex on Thursday March 14, 2024 @04:10PM (#39708416)
I’m talking about the pricing disaster that happened in 2017/2018 where user prices went up from 10x-100x because Google wanted to kill the product without actually killing it.
Re:How Figma's databases team lived to tell the scale by tempnow987 on Thursday March 14, 2024 @07:11PM (#39710094)
Didn't they also hammer folks using google maps in a business / cloud context?

I was also an old app engine user, but bailed ages ago (original app engine).

Re:How Figma's databases team lived to tell the scale by jerrygenser on Thursday March 14, 2024 @05:32PM (#39709226)
IoT is one example of a big backbone service that was sunset.
Re:How Figma's databases team lived to tell the scale by endisneigh on Thursday March 14, 2024 @05:47PM (#39709348)
It had barely any usage though from what I can tell from searching about it.

Not that it’s any solace to those affected.

Re:How Figma's databases team lived to tell the scale by marcinzm on Thursday March 14, 2024 @06:22PM (#39709639)
AI Platform is a recent example that’s been deprecated.
Re:How Figma's databases team lived to tell the scale by rockostrich on Thursday March 21, 2024 @02:49PM (#39782767)
Wasn't it just superseded by Vertex AI? According to the banner announcement in the docs: > All the functionality of legacy AI Platform and new features are available on the Vertex AI platform.