The GCP LB is, honestly, one of the most impressive pieces of software ever written and unmatched by any other provider.
Also I enjoy that GCP has gRPC support.
21–30 of 40 posts
The GCP LB is, honestly, one of the most impressive pieces of software ever written and unmatched by any other provider.
Also I enjoy that GCP has gRPC support.
Earlier quoted context omitted.
sure. the AWS console has been very hard to use since forever. Some may even go as far as saying that it improved. The UX is not the selling point of a cloud provider.
disagree. I get the sentiment that in the long run an end-user absolutely "shouldn't care", because the infrastructure should be code, if the initial end user onramp sucks (bad UX) then it might give you a negative impression of the system. This impacts other end users, because if adoption has a negative first derivative, you could be in trouble in the long run. but UX goes beyond just clicky bits on the web. It's al…
Both AWS and GCP excel over Azure. Many organizations are strong armed into using Azure as part of their Enterprise Agreements (EA) as part of Microsoft's predatory tactics (they haven't changed one bit) I couldn't imagine someone choosing to use Azure if given a choice.
Azure App Services and SQL database arrives a 1-2 punch for enterprises moving their apps to a PaaS that just works.
Both AWS and GCP excel over Azure. Many organizations are strong armed into using Azure as part of their Enterprise Agreements (EA) as part of Microsoft's predatory tactics (they haven't changed one bit) I couldn't imagine someone choosing to use Azure if given a choice.
I think a lot of the issues with AWS mentioned here are mainly the result of 2 factors: 1. AWS having been around longer, and having been vastly bigger and more widely used than GCP for the entire lifespan of both products. AWS is just more expansive/evolved from having piled on more features for more customers over more time. 2. AWS virtually never makes backward-incompatible changes. Every feature of every service…
I think a lot of the issues with AWS mentioned here are mainly the result of 2 factors: 1. AWS having been around longer, and having been vastly bigger and more widely used than GCP for the entire lifespan of both products. AWS is just more expansive/evolved from having piled on more features for more customers over more time. 2. AWS virtually never makes backward-incompatible changes. Every feature of every service…
Has Google EOL any Cloud products? I don't remember any being shutdown recently at least. Since these are money-making products (unlike maybe other good customer-facing products), there's a lot less reasons to shut things down IMO
afaics its called cloud talent in the console now
As someone that works solely in a GCP environment for work, I couldn't agree more. GCP products do "just work", but if I had to nitpick, it's that some of their services don't have complete terraform modules (looking at you IAP), but outside of that, their pricing is reasonable, documentation is solid, and we're really happy we ended up going the GCP route.
Just this week I updated an EKS cluster from 1.15 to 1.16 with two clicks.
Earlier quoted context omitted.
Imagine you running large database workload and AWS say you need reboot because underlying hardware start having issue. Live migration can help you in that case.
1. use RDS 2. if you want to run your own you’d better know how HA setups work and you can lose at least a machine at ANY point in time (not just when AWS warns you the hardware is failing)