Re:Google Cloud networking issues in us-east1
by benbro on Tuesday July 02, 2019 @04:10PM
(#20338970)
Is it practical to use several providers when egress is so expensive?
[ Parent
| on HN ]
Re:Google Cloud networking issues in us-east1
by opportune on Tuesday July 02, 2019 @04:15PM
(#20339016)
No, not unless you are someone like Netflix. Usually you can configure multi-region failover and such and that will keep your things running. It is more expensive but for most use cases I think the cost is still less than the dev time/complexity of setting up multi-provider workflows and the inevitable duplication of resources (which is part of the cost of multi-region anyway)
Re:Google Cloud networking issues in us-east1
by mbesto on Tuesday July 02, 2019 @04:48PM
(#20339276)
No. And there's been a lot of talk recently about multi-provider being the right strategy to mitigate downtime, which IMHO is a farce peddled by expensive consultants. The parent comment is correct - this is why availability zones and regions have been established by each provider.
For the large majority of businesses investing in infrastructure-as-code far outweighs any crazy HA, redundant, multi-provider, whizzbang whatever setup you may have.
Re:Google Cloud networking issues in us-east1
by dragonwriter on Tuesday July 02, 2019 @05:58PM
(#20339752)
> this is why availability zones and regions have been established by each provider.
But the degree of independence provided by AZs is not constant across providers, despite similar terminology.
You can move 1.6TB between providers in a month for the same price as a single beefy DB server (m4.16xlarge here). That's a whole lot of logical replication..