Live data from Hacker News

Google Cloud Platform – The Good, Bad, and Ugly

deps.co

71–80 of 202 posts

Re: Google Cloud Platform – The Good, Bad, and Ugly

#71
post #5

> Sometimes when browsing documentation for a service or API you will find that the old way is deprecated, but the new way that they recommend you use is still in beta or alpha (!). Familiar.

"Beta" is kind of an awful purgatory state on GCP. We all know that most of their beta stuff is actually really well-tested and stable (it's even mentioned in this article). They also know it themselves and seem to assume that people will be willing to start using their products when they are in beta. However, they have an ill-advised blanket policy that beta products are not covered by SLAs, which ends up meaning th…

I totally agree, this is a serious problem. Because even if you understand that they mean “hey it’s Beta but it’s fine for production”, if you choose to use it and it breaks, all blame will point back to you for making an unwise choice.

There is a terrific explanation of the difference between Alpha, Beta, and Stable in the Istio project [0].

Istio was started by GCP, so while this isn’t officially Google’s definition I imagine it’s peobably the same.

It basically says, Beta is mostly usable in production, but things might change in the future that require work from you to upgrade.

[0] https://istio.io/about/feature-stages/

Re: Google Cloud Platform – The Good, Bad, and Ugly

#72

Most of the AWS complexity issues that the author mentions are actually enterprise / high-scale features. Sure, they are too complicated and unnecessary for small operations, but many large organizations wouldn't even consider a cloud infrastructure provider without those things (comprehensive permission and identity model, discernible region and inter-region model, breadth, and depth in computing types, highly audit…

Easy-to-use permission control doesn't mean simple. For example, you can always use off-the-shelf IAM roles provided by GCP, but you can also mix-match permissions and create your own custom roles.

Also network configuration can be complicated if you track down for the detailed form.

Any specific feature you're looking for is missing in GCP?

Re: Google Cloud Platform – The Good, Bad, and Ugly

#73
post #38

One thing I didn't see mentioned in this article is Firebase. It feels like a hidden gem lurking within the overall GCP offering, and may be overlooked by devs who're not doing mobile-specific work. For me, Firebase was the gateway drug that got me into GCP. I successfully built and hosted the backends for a couple of iOS apps using Firebase. The best parts were cloud functions and built-in sync (including offline/oc…

Yep. Firebase + GCP(app engine) is awesome.

Re: Google Cloud Platform – The Good, Bad, and Ugly

#75
This was one heck of a rundown of different GCP options and problems. I haven't used as many services as the OP, but definitely most things that did overlap pretty much echoed my own experience.

Specifically, support and billing.

We've used Gold support for a while, and our experience wasn't great. Pretty much the same as the OP described with Silver. Perhaps response times were slightly faster I imagine, but I would be surprised if quality was any different.

Regarding billing, we've been going through some kafkaesque cycle there trying to set invoiced billing. I've filled a form on their invoiced billing page, a sales contact talked to me on the phone and I explained everything. She then sent an email asking me to fill another form, which I did, and then got contacted by another billing team who basically sent me to the original page. I explained the situation and they just didn't really seem to care or understand what's going on. They then tried to arrange a call, but missed two schedules that I've set, called the wrong number, wrong country code... Not sure where this phone call would lead. Absolutely mind boggling experience there. Teams don't talk to each other. They send the customer around running in circles. It's amazing that it's happening with one of the most sophisticated companies in the world in the 21st century.

Re: Google Cloud Platform – The Good, Bad, and Ugly

#77
I've not used GCP outside of GCP training courses yet (the quality of these is another matter....), but I did come away thinking the console UX and 'Cloud Shell' thing was absolutely brilliant.

This post was interesting to me as the training course presenters seemed to make out that StackDriver was the best thing since sliced bread, but I guess they have to being Google partners...

Re: Google Cloud Platform – The Good, Bad, and Ugly

#78
One other thing I believe is worth mentioning -- and to be honest I was a bit surprised with -- is the ecosystem around GCP vs AWS.

For example, we were looking for a solid redis hosting service in the EU, and latency is key obviously. There are virtually none with GCP, but quite a few with AWS. I'm pretty sure there are other similar examples with other services.

Re: Google Cloud Platform – The Good, Bad, and Ugly

#79

One other thing I believe is worth mentioning -- and to be honest I was a bit surprised with -- is the ecosystem around GCP vs AWS. For example, we were looking for a solid redis hosting service in the EU, and latency is key obviously. There are virtually none with GCP, but quite a few with AWS. I'm pretty sure there are other similar examples with other services.

> we were looking for a solid redis hosting service in the EU, and latency is key obviously. There are virtually none with GCP

Google Cloud recently released public beta for Memorystore Redis (https://cloud.google.com/memorystore/) which is a hosted opensource Redis on GCP. It is availabe in europe-west1 region so it might suit your needs.

disclaimer: I am an engineer on Memorystore Redis team.

Re: Google Cloud Platform – The Good, Bad, and Ugly

#80
post #45

Earlier quoted context omitted.

Because editing yaml or json sucks.

Linked from Hashicorp’s Getting Started page... https://github.com/terraform-providers/terraform-provider-aw...

Which is neither json or yaml...
Post reply on HN