Single-Region Deployment Paradigm
Single-region Atlas deployments set up cluster nodes within one region of one cloud provider. Single-region deployments to regions that support availability zones offer protection in the case of a zonal outage by automatically rerouting traffic to a node in another availability zone for continuous availability and a smooth user experience. Single-region Atlas deployments are supported on all cluster tiers, so they include less expensive options for non-mission-critical deployments, and, when configured correctly, single-region deployments can support performance and help meet compliance requirements for data sovereignty.
To learn how to configure a single-region deployment, see Create a Cluster in the Atlas documentation.
The following diagram shows a single-region Atlas deployment for regions that support availability zones:
Use Cases for Single-Region Deployments
Single-region deployments are best for the following use cases:
Region-Specific Applications that Require Low Latency and Zonal High Availability (One Cloud Provider)
To improve performance for critical operations, all Atlas deployments allow you to deploy data close to your users' geographic location, which reduces latency. You can configure a single-region deployment for high availability across zones and low latency.
A single-region deployment may be best for you if you have the following requirements:
You want to use one cloud provider
You want to deploy to more than one availability zone for high availability, and you don't need to deploy to more than one region
Your application requires low latency and has a majority of users in one geographic location, since single-region deployments allow you to choose your geographic area.
For example, for an application deployed with AWS with
users primarily located in the eastern US, you can deploy a
single-region deployment to us-east-1
(a region that supports availability zones). This
ensures low latency since all nodes are within the eastern US, while
offering high availability if there's a zonal outage that affects the
primary node.
If your application requires low latency and cross-region or cross-provider high availability, consider a Multi-Region Deployment Paradigm or Multi-Cloud Deployment Paradigm, respectively.
If your application requires low latency for users in any region across a global user base, consider a Global Deployment Paradigm.
Applications that Require Data Sovereignty and Zonal High Availability (One Cloud Provider)
For compliance with data residency laws, data can be partitioned to reside in a specific region, ensuring adherence to local regulations. You can configure a single-region deployment for high zonal availability and data sovereignty.
A single-region deployment may be best for you if you have the following requirements:
You want to use one cloud provider
You want to deploy to more than one availability zone for high availability, and you don't need to deploy to more than one region
Your application requires data sovereignty, since single-region deployments allow you to choose your geographic area.
For example, for an application deployed with AWS that
requires data storage in Europe, you can deploy a single-region
deployment to a region within the EU (such as
eu-west-1, a region that supports availability zones). This
ensures data sovereignty since the region is within the EU, while
offering high availability if there's a zonal outage that affects the
primary node.
Data Sovereignty and High Availability Considerations
For compliance with data residency laws, data can be partitioned to reside in specific regions, ensuring adherence to local regulations. However, deploying to a single region sacrifices high availability if there is a regional outage.
You can configure a multi-region for both high availability and data sovereignty.
For example, for an application deployed with AWS that requires data
storage in Europe, you can deploy a multi-region deployment
to three regions within the EU (such as eu-west-1,
eu-west-2, and eu-west-3). This ensures data sovereignty since all
regions are within the EU, while offering high availability if there's a
regional outage that affects one of the nodes.
If your application requires data sovereignty and cross-region or cross-provider high availability, consider a Multi-Region Deployment Paradigm or Multi-Cloud Deployment Paradigm, respectively.
Considerations for Single-Region Deployments
Other considerations for single-region deployments include:
High availability depends on the deployment of nodes across regions as well as the number, distribution, and priority order of nodes. To learn more about recommended cluster topologies for high availability, see Guidance for Atlas High Availability.
For more considerations, see Considerations in the Atlas documentation.
Recommendations for Single-Region Deployments
To learn about recommendations that apply single-region deployments, see the following sections:
To find recommendations for your Atlas cloud deployments, refer to the following resources:
Operational Efficiency
Security
Reliability
Performance
Cost Optimization