Google Cloud Platform – The Good, Bad, and Ugly
1–10 of 202 posts
Re: Google Cloud Platform – The Good, Bad, and Ugly
#2Re: Google Cloud Platform – The Good, Bad, and Ugly
#3Re: Google Cloud Platform – The Good, Bad, and Ugly
#4Re: Google Cloud Platform – The Good, Bad, and Ugly
#5Familiar.
Re: Google Cloud Platform – The Good, Bad, and Ugly
#6Re: Google Cloud Platform – The Good, Bad, and Ugly
#7Things I would add to the Good side.
- ability to commit to multi year cpu/ram without upfront costs
- they can live migrate your vm to new physical hardware, so no need to have random reboots of your instances
- https load balancers allow traffic around the world to enter google network closest to user, this reduces handshakes and reduces comcast like outages to affect users.
the above greatly decrease my stress.
Re: Google Cloud Platform – The Good, Bad, and Ugly
#8Re: Google Cloud Platform – The Good, Bad, and Ugly
#9> 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.
On the other hand, the article doesn’t mention Stackdriver Profiler, which has an amazing UX. Definitely recommended if you are spending significant money on CPU at GCE.
Re: Google Cloud Platform – The Good, Bad, and Ugly
#10well written. Things I would add to the Good side. - ability to commit to multi year cpu/ram without upfront costs - they can live migrate your vm to new physical hardware, so no need to have random reboots of your instances - https load balancers allow traffic around the world to enter google network closest to user, this reduces handshakes and reduces comcast like outages to affect users. the above greatly decrease…