Skip to content

Commit 2a2a865

Browse files
OvhValentinOvhValentin
committed
feat(databases): new guide about comparison of the databases deployment modes
1 parent 1e3ddb5 commit 2a2a865

File tree

3 files changed

+158
-0
lines changed

3 files changed

+158
-0
lines changed

‎pages/public_cloud/public_cloud_databases/databases_regions_comparison/guide.en-gb.md

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: "Comparison of Public Cloud managed databases Deployment Modes - Understanding 3-AZ / 1-AZ"
3+
excerpt: "Explore OVHcloud's managed databases deployment modes"
4+
updated: 2025-05-23
5+
---
6+
7+
## Objective
8+
9+
OVHcloud offers two deployment modes for its [Public Cloud Databases](/links/public-cloud/databases) service, 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.
10+
11+
## Concepts
12+
13+
OVHcloud managed databases offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance:
14+
15+
1. **1-AZ Region**:
16+
2. **3-AZ Region**:
17+
18+
## Deployment modes
19+
20+
> [!primary]
21+
>
22+
> The following information pertains to the different deployment modes available in OVHcloud’s managed databases service. Select the mode that best suits your needs based on resilience, availability, and performance.
23+
24+
### 1-AZ Region
25+
26+
#### Infrastructure and Redundancy
27+
28+
A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same region**, utilizing a 2N+1 redundancy design. This setup offers resilience against server and disk failures but may be vulnerable to a complete data center outage. Note that in a 1-AZ region, the databases service is located in a specific data center, and if an outage occurs in the specific data center hosting the databases service, access to data could be impacted, even if other data centers in the zone remain operational.
29+
30+
#### Characteristics
31+
32+
- **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.
33+
- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones.
34+
- **characteristic:**
35+
36+
#### Limitations
37+
38+
- **Single Point of Failure:** In a 1-AZ region, the databases Engine is deployed within a specific data center. If this data center experiences an outage, access to your databases services could be impacted, even if other data centers within the same availability zone remain operational.
39+
40+
#### Redundancy Specifications for 1-AZ
41+
42+
| Specification | Description |
43+
|-------------------|---------------------------------------------------------------------------|
44+
| **Redundancy Type** | 2N+1 across multiple data centers |
45+
| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . |
46+
| **Use Case Examples** | Suitable for development, testing, and non-critical databases workloads where cost-effectiveness is prioritized over maximum availability. |
47+
48+
<a name="3azregion"></a>
49+
50+
### 3-AZ Region
51+
52+
#### Infrastructure and Redundancy
53+
54+
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.
55+
56+
#### Characteristics
57+
58+
- **High Availability:** The databases Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage.
59+
- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss.
60+
- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for databases workloads.
61+
62+
#### Ideal Use Cases
63+
64+
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.
65+
66+
#### Performance Specifications for 3-AZ
67+
68+
| Specification | Description |
69+
|-------------------|---------------------------------------------------------------------------|
70+
| **Connectivity** | Low latency between availability zones |
71+
| **High Availability** | Maintains access even in the event of zone failures |
72+
| **Use Case Examples** | Mission-critical and availability-sensitive applications , e-commerce, healthcare platforms, financial services, or live-streaming applications. |
73+
74+
## Go Further
75+
76+
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.
77+
78+
Join our [community of users](/links/community) and visit our [Discord channel](https://discord.gg/ovhcloud).

‎pages/public_cloud/public_cloud_databases/databases_regions_comparison/guide.fr-fr.md

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: "Comparison of Public Cloud managed databases Deployment Modes - Understanding 3-AZ / 1-AZ"
3+
excerpt: "Explore OVHcloud's managed databases deployment modes"
4+
updated: 2025-05-23
5+
---
6+
7+
## Objective
8+
9+
OVHcloud offers two deployment modes for its [Public Cloud Databases](/links/public-cloud/databases) service, 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.
10+
11+
## Concepts
12+
13+
OVHcloud managed databases offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance:
14+
15+
1. **1-AZ Region**:
16+
2. **3-AZ Region**:
17+
18+
## Deployment modes
19+
20+
> [!primary]
21+
>
22+
> The following information pertains to the different deployment modes available in OVHcloud’s managed databases service. Select the mode that best suits your needs based on resilience, availability, and performance.
23+
24+
### 1-AZ Region
25+
26+
#### Infrastructure and Redundancy
27+
28+
A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same region**, utilizing a 2N+1 redundancy design. This setup offers resilience against server and disk failures but may be vulnerable to a complete data center outage. Note that in a 1-AZ region, the databases service is located in a specific data center, and if an outage occurs in the specific data center hosting the databases service, access to data could be impacted, even if other data centers in the zone remain operational.
29+
30+
#### Characteristics
31+
32+
- **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.
33+
- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones.
34+
- **characteristic:**
35+
36+
#### Limitations
37+
38+
- **Single Point of Failure:** In a 1-AZ region, the databases Engine is deployed within a specific data center. If this data center experiences an outage, access to your databases services could be impacted, even if other data centers within the same availability zone remain operational.
39+
40+
#### Redundancy Specifications for 1-AZ
41+
42+
| Specification | Description |
43+
|-------------------|---------------------------------------------------------------------------|
44+
| **Redundancy Type** | 2N+1 across multiple data centers |
45+
| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . |
46+
| **Use Case Examples** | Suitable for development, testing, and non-critical databases workloads where cost-effectiveness is prioritized over maximum availability. |
47+
48+
<a name="3azregion"></a>
49+
50+
### 3-AZ Region
51+
52+
#### Infrastructure and Redundancy
53+
54+
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.
55+
56+
#### Characteristics
57+
58+
- **High Availability:** The databases Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage.
59+
- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss.
60+
- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for databases workloads.
61+
62+
#### Ideal Use Cases
63+
64+
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.
65+
66+
#### Performance Specifications for 3-AZ
67+
68+
| Specification | Description |
69+
|-------------------|---------------------------------------------------------------------------|
70+
| **Connectivity** | Low latency between availability zones |
71+
| **High Availability** | Maintains access even in the event of zone failures |
72+
| **Use Case Examples** | Mission-critical and availability-sensitive applications , e-commerce, healthcare platforms, financial services, or live-streaming applications. |
73+
74+
## Go Further
75+
76+
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.
77+
78+
Join our [community of users](/links/community) and visit our [Discord channel](https://discord.gg/ovhcloud).

‎pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
id: 7f1ac99b-28a7-464f-ad68-05f5d83a4a61
2+
full_slug: public-cloud-databases-regions-comparison

0 commit comments

Comments
 (0)