[pirsquare]

Hi everyone, I'm the customer in this case. Wanted to let everyone know that this sort of abrupt suspension for production apps has been a recurring issue that has happened time and again with Google Clown Platform.

Similar horror stories:

https://news.ycombinator.com/item?id=32547912

https://news.ycombinator.com/item?id=33737577

-----

[Update 1]

Yes I agree I have some fault for the initial suspension, but that's not the biggest issue here.

The biggest issue for me is how they "react" to help a customer get things back to normal when something goes wrong.

First, I had to wait for 8 hrs for their Trust and Safety team.

Then it was 24-48 hrs. See https://imgur.com/a/i0OHXcI

Until now I still haven't had a resolution.

And the most ridiculous part is they could still tell me "I just received an email from the Trust and Safety team and they mentioned that they have sent you a separate email." when I had replied 3 times within an hour after they requested for more details. See proof https://imgur.com/a/1ZSmGBH

[ashwagary]

I wonder if there is a cheap existing solution to use multiple cloud hosts at once and minimize this risk instead of moving all eggs to the AWS basket.

[ChatGTP]

Well if you deploy to Kubernetes it standardizes thee APIs you're using to deploy with quite a lot, then you can move around easier.

[LeBit]

I've been trying very hard to sell that idea to my team.

But no, they insist on using every product the different cloud providers offers. This, IMO, is a recipe to lock yourself to vendors and make maintenance and interoperability a nightmare.

It feels like when devs felt they had to use all the gang of four design patterns.

[vasco]

You need to follow some engineering standard. If your engineering org is not optimising away vendor lockin, blocking someone from using tailored-feature-number-367 is unlikely to have any positive effect and you'll just make everyone move slower. If avoiding vendor lock-in is something the org cares about and is doing properly, yeah sure, enforce it, otherwise I've seen many people fighting windmills on this and bikeshedding about "not getting locked-in" when effectively many other things already lock you into that vendor.

[apple4ever]

If you have any fault it's very tiny. Those type of "important" emails are too common. And no warning is ridiculous too.

[m00dy]

I rent one of dedicated machines in Hetzner. Cheap and performant.

[twawaaay]

It is also a different product from Google Cloud or AWS.

[favaq]

Why do you use a hosting solution that you yourself call "Google Clown" ?

[siva7]

Probably because OP didn't call it that back then

[jeffwask]

We don't all always get a choice. We are often left with the inherited sins of our forerunners.

[sourcecodeplz]

> Then it was 24-48 hrs. See https://imgur.com/a/i0OHXcI

Usually I don't care much for grammatical errors, as long as the point gets across clearly. In this case I don't know why it irks me.