- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
We are talking about multi-site Active/Active solution here. That means both sites are actively writing and syncing. If local copy fails, it's not about failing over for the DB but it just need a single retry from application side to read/write the data. We refer to this type of availability as continuous availability, to distinguish it from the high availability where there is brief downtime during failover.
Ideally there is no failover here as second copy in other region is active and up-to-date. e.g https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-multi-master.html
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a 2 ans
- Réponse acceptéedemandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un mois