By using AWS re:Post, you agree to the Terms of Use

Mutli-site Active/Active Disaster Recovery (DR) Architecture on AWS

0

Hi guys!

I'm researching DR on AWS and when I read the Active/Active strategy, I see that AWS notes this strategy is zero downtime. I don't understand why this is zero downtime.

For example, when customers are accessing our app in one region, when this region is down so the customers still have lost connection and then waiting for failing over to the new region. I think there is still downtime but it is very short.

Could you please explain more detail about this problem?

https://aws.amazon.com/blogs/architecture/disaster-recovery-dr-architecture-on-aws-part-i-strategies-for-recovery-in-the-cloud/

Enter image description here

asked 2 months ago37 views
1 Answer
1

It depends on the nature of the service you're providing, in particular how you're storing state and data. If the service is stateless then users can be redirected to a working region as soon as Route53 deems the failed region unhealthy. In a more realistic scenario it's likely some existing sessions might be lost or delayed since the limits of CAP will be reached, but new sessions could be served from the healthy region.

answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions