A data residency policy specifies where data may be stored or processed. In Atlas, it supports compliance by keeping designated data within selected geographic regions while also addressing latency and availability. section 10.3 section 20.1
Implement residency requirements with Atlas Global Clusters by:
- Defining geographic zones, each containing at least one shard, so regional data can use local read and write paths. section 10.3
- Selecting single-region or multiregion zones according to locality, resilience, and read-latency needs. section 10.3
- Assigning Highest Priority, Electable, Read-only, or Analytics regions within each zone to balance writes, failover, and reads. section 10.3
- Choosing the cloud provider, geographic regions, and infrastructure tier during customer-side configuration. section 20.1
Table 10.4 MongoDB Atlas region types
| Region type |
Description |
| Highest Priority |
Region where Atlas deploys the primary replica set member. Clients can issue only write operations to the primary. This region’s location helps you construct a map for directing write operations to the correct zone. |
| Electable |
Region where Atlas deploys electable secondary replica set members, providing additional fault tolerance in case of a regional outage in the Highest Priority region. |
| Read-only |
Region where Atlas deploys nonelectable secondary replica set members to support secondary read. |
Use the region-type table to compare how Highest Priority, Electable, and Read-only regions implement writes, fault tolerance, and secondary reads. section 10.3
