diff --git a/pages/index.md b/pages/index.md index adb21ab2525..c9c0bb5093d 100644 --- a/pages/index.md +++ b/pages/index.md @@ -732,6 +732,7 @@ + [Responsibility model](public_cloud/public_cloud_databases/information_03_shared_responsibility) + [FAQ Public Cloud databases](public_cloud/public_cloud_databases/information_04_faq) + [Public Cloud Databases - Capabilities and Limitations](public_cloud/public_cloud_databases/information_05_capabilities) + + [Comparison of Public Cloud Databases Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/public_cloud_databases/databases_18_regions_comparison) + [Public Cloud Databases - Maintenance operations](public_cloud/public_cloud_databases/databases_15_maintenances) + [Public Cloud Databases - Automated Backups](public_cloud/public_cloud_databases/databases_05_automated_backups) + [General guides](public-cloud-databases-general-guides) diff --git a/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/guide.en-gb.md new file mode 100644 index 00000000000..1188c3ba36b --- /dev/null +++ b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/guide.en-gb.md @@ -0,0 +1,56 @@ +--- +title: "Comparison of Public Cloud Databases Deployment Modes - Understanding 3-AZ / 1-AZ" +excerpt: "Explore OVHcloud's Public Cloud Databases deployment modes" +updated: 2025-06-11 +--- + +## Objective + +OVHcloud offers two deployment modes for its [Public Cloud Databases](/links/public-cloud/databases) services, each tailored to specific needs regarding resilience, availability, performance, and latency. This document provides a detailed explanation of the characteristics of each deployment mode, followed by a comprehensive comparison to help users choose the best option for their requirements. + +## Concepts + +OVHcloud managed databases offer two main deployment modes, each optimized for specific use cases and offering various levels of resilience and failover: + +1. **1-AZ Region**: for standard applications, offering basic resilience with optimized cost. +2. **3-AZ Region**: suitable for applications that handle highly critical data or require high availability with low RTO/RPO and resilience to availability zone outage. + +## Deployment modes + +> [!primary] +> +> The following information pertains to the different deployment modes available in OVHcloud’s managed database service. Select the mode that best suits your needs based on resilience, availability, and performance. + +### 1-AZ Region + +A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a database service is deployed with multiple nodes, this single AZ setup offers resilience against node and disk failures but may be vulnerable to a complete OpenStack region outage. Note that in a 1-AZ region, the database service is located in a specific OpenStack region that spans over multiple data centers. The nodes of a multi-node database service are scattered in different hosts that **may be** located in different data centers. If an outage occurs in a specific data center hosting one or multiple nodes of the database service, access to data could be impacted, even if other data centers in the zone remain operational. + +#### Characteristics + +- **Cost-Effectiveness:** Deploying in a 1-AZ region is generally more affordable, making it suitable for development, testing, and non-critical workloads where cost considerations are paramount. +- **Host antiaffinity:** The nodes of a multi-node database service are deployed in different physical hosts offering resilience to host outage. + +#### Limitations + +- **Single Point of Failure:** In a 1-AZ region, the database services nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your database services could be impacted, even if other data centers within the same availability zone remain operational. + + + +### 3-AZ Region + +3-AZ Regions consist of **three independent availability zones**, each isolated in terms of power, cooling, and network systems, providing true fault isolation. This architecture ensures **service availability** even if an entire availability zone experiences an outage. + +#### Characteristics + +- **High Availability:** Multi-node database service is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage. +- **Low Latency:** The architecture offers ultra-low latency between availability zones, ensuring performance of database read/write operations on primary and standby nodes. + +#### Ideal Use Cases + +3-AZ Regions are particularly suited to mission-critical and availability-sensitive applications, where data governance requires continuous availability. This includes sectors such as e-commerce, healthcare platforms, financial services or live streaming applications. + +## Go Further + +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case. + +Join our [community of users](/links/community) and visit our [Discord channel](https://discord.gg/ovhcloud). \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml new file mode 100644 index 00000000000..34a4039be0f --- /dev/null +++ b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml @@ -0,0 +1,2 @@ +id: 7f1ac99b-28a7-464f-ad68-05f5d83a4a61 +full_slug: public-cloud-databases-regions-comparison \ No newline at end of file