Multi-region architecture

A cloud region is a group of data centers in one geographic area, like Northern Virginia or São Paulo. Spreading an app across availability zones inside one region already protects it from losing a single building. A multi-region architecture goes further: it runs the application in two or more regions, often far apart, so it keeps working even if an entire region fails, and so users far away get answers from a closer place.

There are two main styles. In active-passive, one region serves all the traffic and another keeps a copy ready to take over; DNS or a global load balancer moves users when the main one fails. In active-active, every region serves users at the same time. Active-active is faster for a global audience and fails over more smoothly, but it is much harder to build.

The hard part is the data. Copying a database between regions takes time, because distance adds latency, so at any moment the copies can be slightly behind. Two users editing the same record in different regions can conflict. Teams must choose between waiting for every region to agree, which is slow, or accepting a small window of changes that could be lost or reconciled later. On top of that you pay for servers and data transfer in every region, and some laws limit where personal data can go. That is why many companies keep multi-region for their most critical systems.