3 ms·

The Spinnaker project is looking more appealing with every outage. Outage detected in X provider in Y region? Deploy infrastructure to Z provider in Y region.

by xyst 7y ago

MuffinFlavored 7y ago
From their Multi-Cloud section on their homepage: > Deploy across multiple cloud providers including AWS EC2, Kubernetes Kubernetes... where?
- mooreds 7y ago
  Probably self hosted.
bjterry 7y ago
This outage is only affecting a single availability zone, so taking on the complexity of multiple cloud providers would not be necessary to be resilient against it. AWS best practices would already have covered you.
- herostratus101 7y ago
  Where does it say it's a single AZ?
  - judge2020 7y ago
    Every "more" drawer/dropdown > We are investigating connectivity issues affecting some single-AZ RDS instances in a single Availability Zone in the US-EAST-1 Region.
- kortilla 7y ago
  AWS best practices involve using AWS for everything, which is not actually a best practice.
herostratus101 7y ago
Lol, or just architect your applications to be highly available and fault-tolerant to regional failures if that's your business requirement.
cstejerean 7y ago
Or just deploy to us-west-2 (or maybe us-east-2) in the first place and then enjoy not having to do anything every time there’s an outage in us-east-1, which is where pretty much all the AWS outages are. And if there is an issue for some reason failing over to another AWS region is a lot easier than having to fail over to another cloud provider. Outside of a very small number of cases building for multi-cloud is a lot of unnecessary work.
aeyes 7y ago
Deploying a database with 5 TB on disk and 50k data-modifying transactions per second to multiple providers isn't exactly trivial. Who cares about stateless, that's a solved problem.
- slisznia 7y ago
  The volume and storage numbers you quoted call for breaking up a monolithic system. We have a similar overall volume of transactions and storage needs to yours but we reside in all US regions, tens of AZs. If one AZ went down, a small fraction of customers would be affected. True, we have increased our exposure to an outage happening somewhere but we improved overall business continuity. Simply put, dealing with 5% of pissed customers is easier than 50% or all of them calling you at once.

The Spinnaker project is looking more appealing with every outage. Outage detected in X provider in Y region? Deploy infrastructure to Z provider in Y region.

by xyst 7y ago

The Spinnaker project is looking more appealing with every outage. Outage detected in X provider in Y region? Deploy infrastructure to Z provider in Y region.

MuffinFlavored 7y ago

From their Multi-Cloud section on their homepage: > Deploy across multiple cloud providers including AWS EC2, Kubernetes Kubernetes... where?

mooreds 7y ago
Probably self hosted.

bjterry 7y ago

This outage is only affecting a single availability zone, so taking on the complexity of multiple cloud providers would not be necessary to be resilient against it. AWS best practices would already have covered you.

herostratus101 7y ago
Where does it say it's a single AZ?
- judge2020 7y ago
  Every "more" drawer/dropdown > We are investigating connectivity issues affecting some single-AZ RDS instances in a single Availability Zone in the US-EAST-1 Region.
kortilla 7y ago
AWS best practices involve using AWS for everything, which is not actually a best practice.

herostratus101 7y ago

Lol, or just architect your applications to be highly available and fault-tolerant to regional failures if that's your business requirement.

cstejerean 7y ago

Or just deploy to us-west-2 (or maybe us-east-2) in the first place and then enjoy not having to do anything every time there’s an outage in us-east-1, which is where pretty much all the AWS outages are. And if there is an issue for some reason failing over to another AWS region is a lot easier than having to fail over to another cloud provider. Outside of a very small number of cases building for multi-cloud is a lot of unnecessary work.

aeyes 7y ago

Deploying a database with 5 TB on disk and 50k data-modifying transactions per second to multiple providers isn't exactly trivial. Who cares about stateless, that's a solved problem.

slisznia 7y ago
The volume and storage numbers you quoted call for breaking up a monolithic system. We have a similar overall volume of transactions and storage needs to yours but we reside in all US regions, tens of AZs. If one AZ went down, a small fraction of customers would be affected. True, we have increased our exposure to an outage happening somewhere but we improved overall business continuity. Simply put, dealing with 5% of pissed customers is easier than 50% or all of them calling you at once.