From 74c21596a1603b80b4cda3c9d814a31d3d7b49b1 Mon Sep 17 00:00:00 2001 From: Valentin Lacour Date: Tue, 13 May 2025 13:51:50 +0200 Subject: [PATCH 1/5] feat(analytics): create guide about comparison of analytics deployment modes --- .../guide.en-gb.md | 78 +++++++++++++++++++ .../guide.fr-fr.md | 78 +++++++++++++++++++ .../analytics_regions_comparison/meta.yaml | 2 + .../databases_regions_comparison/meta.yaml | 2 + 4 files changed, 160 insertions(+) create mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md create mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md create mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml create mode 100644 pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md new file mode 100644 index 00000000000..1fd114b5185 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md @@ -0,0 +1,78 @@ +--- +title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" +excerpt: "Explore OVHcloud's Analytics engines deployment modes" +updated: 2025-05-23 +--- + +## Objective + +OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/analytics) 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. + +## Concepts + +OVHcloud Analytics offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance: + +1. **1-AZ Region**: +2. **3-AZ Region**: + +## Deployment modes + +> [!primary] +> +> The following information pertains to the different deployment modes available in OVHcloud’s Analytics service. Select the mode that best suits your needs based on resilience, availability, and performance. + +### 1-AZ Region + +#### Infrastructure and Redundancy + +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 Analytics service is located in a specific data center, and if an outage occurs in the specific data center hosting the Analytics 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. +- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones. +- **characteristic:** + +#### Limitations + +- **Single Point of Failure:** In a 1-AZ region, the Analytics Engine is deployed within a specific data center. If this data center experiences an outage, access to your analytics services could be impacted, even if other data centers within the same availability zone remain operational. + +#### Redundancy Specifications for 1-AZ + +| Specification | Description | +|-------------------|---------------------------------------------------------------------------| +| **Redundancy Type** | 2N+1 across multiple data centers | +| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . | +| **Use Case Examples** | Suitable for development, testing, and non-critical analytics workloads where cost-effectiveness is prioritized over maximum availability. | + + + +### 3-AZ Region + +#### Infrastructure and Redundancy + +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:** The Analytics Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage. +- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss. +- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for analytics workloads. + +#### 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. + +#### Performance Specifications for 3-AZ + +| Specification | Description | +|-------------------|---------------------------------------------------------------------------| +| **Connectivity** | Low latency between availability zones | +| **High Availability** | Maintains access even in the event of zone failures | +| **Use Case Examples** | Mission-critical and availability-sensitive applications , 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/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md new file mode 100644 index 00000000000..1fd114b5185 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md @@ -0,0 +1,78 @@ +--- +title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" +excerpt: "Explore OVHcloud's Analytics engines deployment modes" +updated: 2025-05-23 +--- + +## Objective + +OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/analytics) 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. + +## Concepts + +OVHcloud Analytics offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance: + +1. **1-AZ Region**: +2. **3-AZ Region**: + +## Deployment modes + +> [!primary] +> +> The following information pertains to the different deployment modes available in OVHcloud’s Analytics service. Select the mode that best suits your needs based on resilience, availability, and performance. + +### 1-AZ Region + +#### Infrastructure and Redundancy + +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 Analytics service is located in a specific data center, and if an outage occurs in the specific data center hosting the Analytics 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. +- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones. +- **characteristic:** + +#### Limitations + +- **Single Point of Failure:** In a 1-AZ region, the Analytics Engine is deployed within a specific data center. If this data center experiences an outage, access to your analytics services could be impacted, even if other data centers within the same availability zone remain operational. + +#### Redundancy Specifications for 1-AZ + +| Specification | Description | +|-------------------|---------------------------------------------------------------------------| +| **Redundancy Type** | 2N+1 across multiple data centers | +| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . | +| **Use Case Examples** | Suitable for development, testing, and non-critical analytics workloads where cost-effectiveness is prioritized over maximum availability. | + + + +### 3-AZ Region + +#### Infrastructure and Redundancy + +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:** The Analytics Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage. +- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss. +- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for analytics workloads. + +#### 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. + +#### Performance Specifications for 3-AZ + +| Specification | Description | +|-------------------|---------------------------------------------------------------------------| +| **Connectivity** | Low latency between availability zones | +| **High Availability** | Maintains access even in the event of zone failures | +| **Use Case Examples** | Mission-critical and availability-sensitive applications , 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/data_analytics/analytics/analytics_regions_comparison/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml new file mode 100644 index 00000000000..5da18d61238 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml @@ -0,0 +1,2 @@ +id: 0041c9bd-8bf4-493a-8414-4c05349264f9 +full_slug: data-analytics-regions-comparison \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml new file mode 100644 index 00000000000..fe56573d970 --- /dev/null +++ b/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml @@ -0,0 +1,2 @@ +id: ad86ded9-70e2-458a-9d5e-bee258c5eaae +full_slug: public-cloud-databases-regions-comparison \ No newline at end of file From 5c39e3cb67b97cd81f3d4a227cc7dba39f0834ce Mon Sep 17 00:00:00 2001 From: Valentin Lacour Date: Tue, 13 May 2025 14:02:46 +0200 Subject: [PATCH 2/5] delete folder --- .../databases_regions_comparison/meta.yaml | 2 -- 1 file changed, 2 deletions(-) delete mode 100644 pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml diff --git a/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml deleted file mode 100644 index fe56573d970..00000000000 --- a/pages/public_cloud/public_cloud_databases/databases_regions_comparison/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: ad86ded9-70e2-458a-9d5e-bee258c5eaae -full_slug: public-cloud-databases-regions-comparison \ No newline at end of file From 3784c364cbe09c1b537dfcc5c585855038fc553f Mon Sep 17 00:00:00 2001 From: Thibaud Le Douarin Date: Tue, 3 Jun 2025 15:27:07 +0200 Subject: [PATCH 3/5] Update the guide with PMM feedbacks --- .../guide.en-gb.md | 44 +++-------- .../guide.fr-fr.md | 78 ------------------- 2 files changed, 11 insertions(+), 111 deletions(-) delete mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md index 1fd114b5185..85c57a5396a 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" -excerpt: "Explore OVHcloud's Analytics engines deployment modes" -updated: 2025-05-23 +excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes" +updated: 2025-05-27 --- ## Objective @@ -10,67 +10,45 @@ OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/ana ## Concepts -OVHcloud Analytics offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance: +OVHcloud managed analytics services offer two main deployment modes, each optimized for specific use cases and offering various levels of resilience and failover: -1. **1-AZ Region**: -2. **3-AZ Region**: +1. **1-AZ Region**: for standard analytics workloads, offering basic resilience with optimized cost. +2. **3-AZ Region**: suitable for highly availability analytics workloads 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 Analytics service. Select the mode that best suits your needs based on resilience, availability, and performance. +> The following information pertains to the different deployment modes available in OVHcloud’s Analytics services. Select the mode that best suits your needs based on resilience, availability, and performance. ### 1-AZ Region -#### Infrastructure and Redundancy - -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 Analytics service is located in a specific data center, and if an outage occurs in the specific data center hosting the Analytics service, access to data could be impacted, even if other data centers in the zone remain operational. +A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a multi-node analytics service is deployed, 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 analytics service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node analytics 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 analytics 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. -- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones. -- **characteristic:** +- **Host antiaffinity:** The nodes of a multi-node analytics service are deployed in different physical hosts offering resilience to host outage. #### Limitations -- **Single Point of Failure:** In a 1-AZ region, the Analytics Engine is deployed within a specific data center. If this data center experiences an outage, access to your analytics services could be impacted, even if other data centers within the same availability zone remain operational. - -#### Redundancy Specifications for 1-AZ - -| Specification | Description | -|-------------------|---------------------------------------------------------------------------| -| **Redundancy Type** | 2N+1 across multiple data centers | -| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . | -| **Use Case Examples** | Suitable for development, testing, and non-critical analytics workloads where cost-effectiveness is prioritized over maximum availability. | +- **Single Point of Failure:** In a 1-AZ region, the analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your analytics service could be impacted, even if other data centers within the same availability zone remain operational. ### 3-AZ Region -#### Infrastructure and Redundancy - 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:** The Analytics Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage. -- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss. -- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for analytics workloads. +- **High Availability:** Multi-node analytics 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 analytics operations accross all the nodes of the cluster. #### 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. -#### Performance Specifications for 3-AZ - -| Specification | Description | -|-------------------|---------------------------------------------------------------------------| -| **Connectivity** | Low latency between availability zones | -| **High Availability** | Maintains access even in the event of zone failures | -| **Use Case Examples** | Mission-critical and availability-sensitive applications , 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. diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md deleted file mode 100644 index 1fd114b5185..00000000000 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" -excerpt: "Explore OVHcloud's Analytics engines deployment modes" -updated: 2025-05-23 ---- - -## Objective - -OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/analytics) 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. - -## Concepts - -OVHcloud Analytics offers two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance: - -1. **1-AZ Region**: -2. **3-AZ Region**: - -## Deployment modes - -> [!primary] -> -> The following information pertains to the different deployment modes available in OVHcloud’s Analytics service. Select the mode that best suits your needs based on resilience, availability, and performance. - -### 1-AZ Region - -#### Infrastructure and Redundancy - -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 Analytics service is located in a specific data center, and if an outage occurs in the specific data center hosting the Analytics 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. -- **Simplified Architecture:** The single-zone setup simplifies deployment and management, reducing complexity for teams that do not require high availability across multiple zones. -- **characteristic:** - -#### Limitations - -- **Single Point of Failure:** In a 1-AZ region, the Analytics Engine is deployed within a specific data center. If this data center experiences an outage, access to your analytics services could be impacted, even if other data centers within the same availability zone remain operational. - -#### Redundancy Specifications for 1-AZ - -| Specification | Description | -|-------------------|---------------------------------------------------------------------------| -| **Redundancy Type** | 2N+1 across multiple data centers | -| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk . | -| **Use Case Examples** | Suitable for development, testing, and non-critical analytics workloads where cost-effectiveness is prioritized over maximum availability. | - - - -### 3-AZ Region - -#### Infrastructure and Redundancy - -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:** The Analytics Engine is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage. -- **Fault Tolerance:** With data replicated across all three zones, the system provides robust fault tolerance, minimizing the risk of data loss. -- **Low Latency:** The architecture offers ultra-low latency between availability zones, enhancing performance for analytics workloads. - -#### 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. - -#### Performance Specifications for 3-AZ - -| Specification | Description | -|-------------------|---------------------------------------------------------------------------| -| **Connectivity** | Low latency between availability zones | -| **High Availability** | Maintains access even in the event of zone failures | -| **Use Case Examples** | Mission-critical and availability-sensitive applications , 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 From d80d68a1d8648cf8738432da8631c54927d44571 Mon Sep 17 00:00:00 2001 From: Valentin Lacour Date: Tue, 10 Jun 2025 11:26:21 +0200 Subject: [PATCH 4/5] add fr and add guide in the index --- pages/index.md | 1 + .../guide.en-gb.md | 2 +- .../guide.fr-fr.md | 56 +++++++++++++++++++ 3 files changed, 58 insertions(+), 1 deletion(-) create mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md diff --git a/pages/index.md b/pages/index.md index adb21ab2525..705ff95a58a 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 Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/data_analytics/analytics/analytics_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/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md index 85c57a5396a..bcd4ffb3c0a 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes" -updated: 2025-05-27 +updated: 2025-06-10 --- ## Objective diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md new file mode 100644 index 00000000000..bcd4ffb3c0a --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md @@ -0,0 +1,56 @@ +--- +title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" +excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes" +updated: 2025-06-10 +--- + +## Objective + +OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/analytics) 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. + +## Concepts + +OVHcloud managed analytics services 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 analytics workloads, offering basic resilience with optimized cost. +2. **3-AZ Region**: suitable for highly availability analytics workloads 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 Analytics services. 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 multi-node analytics service is deployed, 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 analytics service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node analytics 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 analytics 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 analytics service are deployed in different physical hosts offering resilience to host outage. + +#### Limitations + +- **Single Point of Failure:** In a 1-AZ region, the analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your analytics service 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 analytics 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 analytics operations accross all the nodes of the cluster. + +#### 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 From c5e617ec78391054b63b76fe449bd49ae405d68c Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Wed, 11 Jun 2025 09:18:21 +0200 Subject: [PATCH 5/5] Date update + proofreading + fr-fr deletion --- .../guide.en-gb.md | 18 +++--- .../guide.fr-fr.md | 56 ------------------- 2 files changed, 9 insertions(+), 65 deletions(-) delete mode 100644 pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md index bcd4ffb3c0a..07ecf6899a6 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes" -updated: 2025-06-10 +updated: 2025-06-11 --- ## Objective @@ -10,10 +10,10 @@ OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/ana ## Concepts -OVHcloud managed analytics services offer two main deployment modes, each optimized for specific use cases and offering various levels of resilience and failover: +OVHcloud managed Analytics services 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 analytics workloads, offering basic resilience with optimized cost. -2. **3-AZ Region**: suitable for highly availability analytics workloads with low RTO/RPO and resilience to availability zone outage. +1. **1-AZ Region**: for standard Analytics workloads, offering basic resilience with optimized cost. +2. **3-AZ Region**: suitable for highly availability Analytics workloads with low RTO/RPO and resilience to availability zone outage. ## Deployment modes @@ -23,16 +23,16 @@ OVHcloud managed analytics services offer two main deployment modes, each optimi ### 1-AZ Region -A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a multi-node analytics service is deployed, 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 analytics service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node analytics 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 analytics service, access to data could be impacted, even if other data centers in the zone remain operational. +A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a multi-node Analytics service is deployed, 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 Analytics service is located in a specific OpenStack region that spans over multiple data centers. The nodes of a multi-node Analytics 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 Analytics 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 analytics service are deployed in different physical hosts offering resilience to host outage. +- **Host antiaffinity:** The nodes of a multi-node Analytics service are deployed in different physical hosts offering resilience to host outage. #### Limitations -- **Single Point of Failure:** In a 1-AZ region, the analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your analytics service could be impacted, even if other data centers within the same availability zone remain operational. +- **Single Point of Failure:** In a 1-AZ region, the Analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your Analytics service could be impacted, even if other data centers within the same availability zone remain operational. @@ -42,8 +42,8 @@ A 1-AZ Region consists of a **single availability zone covering multiple data ce #### Characteristics -- **High Availability:** Multi-node analytics 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 analytics operations accross all the nodes of the cluster. +- **High Availability:** Multi-node Analytics 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 Analytics operations accross all the nodes of the cluster. #### Ideal Use Cases diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md deleted file mode 100644 index bcd4ffb3c0a..00000000000 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.fr-fr.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ" -excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes" -updated: 2025-06-10 ---- - -## Objective - -OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/analytics) 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. - -## Concepts - -OVHcloud managed analytics services 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 analytics workloads, offering basic resilience with optimized cost. -2. **3-AZ Region**: suitable for highly availability analytics workloads 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 Analytics services. 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 multi-node analytics service is deployed, 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 analytics service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node analytics 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 analytics 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 analytics service are deployed in different physical hosts offering resilience to host outage. - -#### Limitations - -- **Single Point of Failure:** In a 1-AZ region, the analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your analytics service 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 analytics 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 analytics operations accross all the nodes of the cluster. - -#### 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