Going Multi-Cloud with AWS and GCP: Lessons Learned at Scale

229 点作者 jbyers超过 7 年前

13 条评论

nodesocket超过 7 年前

One of the biggest benefits of Google Cloud is networking. By default GCE instances in VPC's can communicate with all instances across zones and regions. This is a huge plus.On AWS, multi region involves setting up VPN and NAT instances. Not rocket science, but wasted brain cycles.Generally, with GCP setting up clusters that span three regions should provide ample high availability and most users don't need to deal with the multi cloud headaches. KISS. You can even get pretty good latency between regions if you setup North Carolina, South Carolina, and Iowa. Soon West Coast clusters will be possible between Oregon and Los Angels (region coming soon).

评论 #15069481 未加载

评论 #15069039 未加载

评论 #15069587 未加载

评论 #15071129 未加载

ad_hominem超过 7 年前

If any Google Cloud people are listening I wish you had an equivalent to AWS's Certificate Manager. Provisioning a TLS certificate which automatically renews for eternity (no out-of-band Let's Encrypt renewal process needed) and attaching it to a load balancer is so nice compared to Google Cloud's manual SslCertificate resource creation flow[1].To a lesser extent, it's also nice registering domains within AWS and setting them to auto renew. Since Google Domains already exists, it would be neat to have this feature right inside Google Cloud.[1]: <a href="https://cloud.google.com/compute/docs/load-balancing/http/ssl-certificates" rel="nofollow">https://cloud.google.com/compute/docs/load-balancing/http/ss...</a>

评论 #15069871 未加载

评论 #15070350 未加载

vira28超过 7 年前

One thing that I liked with GCP is their recommendation for cost saving. I spun up a compute engine for a hobby project and within minutes they gave recommendations to reduce the instance size and how much i can save. I don't think AWS offers something like that. Correct me if I am wrong.

评论 #15069254 未加载

评论 #15069105 未加载

azurezyq超过 7 年前

One extra point for tracking VM bills:GCE bills are aggregated across instances. To get more detailed breakdown, you can apply labels to them and the bills will have label information attached in BQ.Alternatively, you can leverage GCE usage exports here:<a href="https://cloud.google.com/compute/docs/usage-export" rel="nofollow">https://cloud.google.com/compute/docs/usage-export</a>Which has per-instance per-day per-item usage data for GCE.Disclosure: I work for Google Cloud but not on GCE.

manigandham超过 7 年前

When it comes to GCP:- They have Role Based Support plans which offer flat prices per subscribed user which is a much better model. [1]- Live migration for VMs mean host maintenance and failures are a minor issue, even if all your apps are running on the same machine. It's pretty much magical and when combined with persistent disks, effectively gives you a very reliable "machine" in the cloud. [2]1. <a href="https://cloud.google.com/support/role-based/" rel="nofollow">https://cloud.google.com/support/role-based/</a>2. <a href="https://cloud.google.com/compute/docs/instances/live-migration" rel="nofollow">https://cloud.google.com/compute/docs/instances/live-migrati...</a>

user5994461超过 7 年前

>>> on AWS you have the option of getting dedicated machines which you can use to guarantee no two machines of yours run on the same underlying motherboard, or you can just use the largest instance type of its class (ex: r3.8xlarge) to probably have a whole motherboard to yourself.Not at all. Major mistake here.When you buy a dedicated instances on AWS, you reserve an entire server for yourself. All the VMs you buy subsequently will go to that same physical machine.In effect, your VMs are on the same motherboard and will all die together if the hardware experiences a failure. It's the exact opposite of what you wanted to do!

评论 #15069297 未加载

评论 #15068957 未加载

评论 #15068969 未加载

dswalter超过 7 年前

If AWS were to go to a per-minute billing cycle, they would be instantly more price-competitive with Google's offering. Or, to put it the other way around, those leftover minutes form a significant chunk of AWS's profit margin.

评论 #15068290 未加载

评论 #15068116 未加载

matt_wulfeck超过 7 年前

> As we investigated growth strategies outside of a single AZ, we realized a lot of the infrastructure changes we needed to make to accommodate multiple availability zones were the same changes we would need to make to accommodate multiple clouds.Maybe he author means multiple regions? Multi az is so easy. Everything works. Multi region is much harder.

whatsmyhandle超过 7 年前

Very nice writeup! A nice, detailed read that was easy to understand.It seems to focus more on raw infrastructure (EC2 vs GCE) instead of each company's PaaS offerings. Obviously AWS has the front runner lead here, but would be super curious in a comparison of RDS vs. Cloud Spanner for instance. (pun unintentional, but then realized, and left in there)

评论 #15069122 未加载

评论 #15069058 未加载

swozey超过 7 年前

Great thorough comparison and falls very into line with my experience. Definitely worth the read. Thanks!

throwaway0071超过 7 年前

Off Topic: it's frustrating that these companies spend quite a lot of time and money learning about the complexities of their infrastructure but when you're interviewing at such companies, you're expected to have answers for everything and a complete strategy for the cloud./rant

hobolord超过 7 年前

Great post! How difficult is it to switch from an AWS EC2 instance to the GCP version?

mrg3_2013超过 7 年前

Nice post! I will be using it as a reference.