Control Plane Architecture for Multi-Zone Data Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data center configurations are vulnerable to network failures, leading to unavailability of computing resources when a single fault zone experiences an outage, as data replication is not adequately distributed across multiple zones, resulting in potential data loss and service disruptions.

Innovation Solution

Implementing a control plane architecture that distributes data replication across multiple fault zones, ensuring that a quorum of control plane instances is maintained outside the affected zone, allowing for continued data availability and fault tolerance by forming a consensus protocol among daemons located in different zones.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is replicated within a single fault zone to maintain simplicity and performance, then data access speed is improved, but system reliability deteriorates when that zone experiences failure

Engineering Contradiction:
Improvedata access speedVSAvoidsystem reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system divides the fault zone into multiple availability zones (AZs) within the same region. Data is replicated across these AZs (e.g., 3 copies distributed across 3 AZs) rather than concentrating all replicas in a single zone. This segmentation ensures that if one AZ fails, data remains accessible from other AZs, resolving the contradiction between maintaining fast local access and ensuring reliability against zone failures.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional organization of data replication by implementing cross-zone replication strategy. Instead of replicating data only within the same fault zone (single-dimension replication), the system replicates data across multiple fault zones (multi-dimension replication). This allows the system to maintain low-latency access within each AZ while providing fault tolerance across zones, effectively resolving the speed-reliability contradiction.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Device complexity

If control plane instances are concentrated in a single fault zone to simplify management, then operational complexity is reduced, but availability deteriorates during zone outages

Engineering Contradiction:
Improvemanagement complexityVSAvoidavailability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The control plane is segmented into multiple independent control plane instances distributed across different fault zones. Each AZ has its own control plane instance that can independently manage data plane resources in that zone. This segmentation allows the system to maintain simple local management within each AZ while ensuring that control functions remain available even if one control plane instance fails due to zone outage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a coordination mechanism (intermediary layer) that enables multiple control plane instances across different zones to work together. This intermediary coordination layer manages the distributed control plane instances, allowing them to maintain consistency and cooperate during failures without requiring complex direct peer-to-peer management between all instances, thus resolving the contradiction between simplified management and high availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If storage volumes are tightly coupled to specific fault zones to optimize performance, then I/O performance is improved, but adaptability deteriorates during network partitions

Engineering Contradiction:
ImproveI/O performanceVSAvoidadaptability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic volume attachment capabilities that allow storage volumes to be detached from failed AZs and reattached to healthy AZs. During normal operation, volumes are tightly coupled to specific AZs for optimal I/O performance. However, when network partitions or failures occur, the system dynamically reconfigures volume attachments to healthy zones, maintaining adaptability without permanently sacrificing performance optimization.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the operational parameters of storage volumes dynamically based on system conditions. Under normal conditions, volumes operate with fixed zone assignments for optimal performance. During failures or network partitions, the system changes the zone assignment parameter, allowing volumes to be moved to different AZs. This parameter change enables the system to adapt to failure conditions while maintaining performance optimization in normal operation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10404613B1Placement of control and data plane resources
Publication Date: 2019.09.03 AMAZON TECH INC
  • US10404613B1 patent drawing
  • US10404613B1 patent drawing
  • US10404613B1 patent drawing

AI summary

Computing resource services have computing resources allocated among regions and data zones, where regions can be completely separate deployments of an infrastructure to provide the highest degree of independence. The more regions that are utilized by a customer, the higher the level of fault tolerance may exist. Current networks consist of heavily distributed infrastructures or mainly centralized infrastructures, both of which can cause complete control plane failures when even a subset of a data zone or region loses network connectivity. The placement of control plane and data plane resources provides for optimal availability and durability during infrastructure failures.