Database Replication Network Layer for Host Version Mismatch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database management systems face challenges in maintaining high availability and minimizing downtime during host upgrades, especially when hosts performing source and replica roles are running different versions, leading to communication issues and potential data corruption.
Innovation Solution
The implementation of a network layer that applies an allow list to requests between hosts, ensuring that only permitted requests, such as those related to replication, are directed to replica hosts, while requests related to active-active arrangements are directed to source hosts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hosts are upgraded to different versions to maintain system availability, then system availability is improved, but communication issues and data corruption risks arise between hosts running different versions
Solution Approach 1:
A network layer is introduced as an intermediary component that sits between hosts running different versions. This network layer translates and routes requests appropriately, allowing communication between hosts with different operating parameters without direct interaction between incompatible versions, thus preventing communication issues and data corruption while maintaining system availability
Solution Approach 2:
The system allows hosts to operate with different version parameters simultaneously by dynamically managing request routing based on host capabilities. The network layer modifies request parameters and routing decisions in real-time, enabling hosts to run at different versions while maintaining compatible communication protocols
2Reliability
If an allow list is applied to requests between hosts, then communication security and data integrity are improved, but system complexity increases
Solution Approach 1:
The request routing functionality is segmented into a separate network layer component, distinct from the host application logic. This allows the allow list mechanism to be implemented and managed independently, reducing the complexity burden on individual hosts while maintaining centralized control over communication security and data integrity
Solution Approach 2:
The network layer acts as an intermediary that centralizes the allow list management logic. By concentrating the complexity in a dedicated routing layer rather than distributing it across all hosts, the system achieves improved communication security while managing overall system complexity in a controlled manner
Data Source
AI summary
Various examples described herein are directed to systems and methods for operating a database management system. A first host may be executed at a first container of a cloud environment. The first host may be configured according to a first set of operating parameters and may perform a source role. A second host may be executed at a second container of the cloud environment. The second host may be configured according to the first set of operating parameters and may perform a replica role or the source role. A request to modify at least one operating parameter of the first source may be received. A third host may be started at a third container and configured to perform at least one of the source role or the replica role for the source role. At least one of the first host or the second host may be shut down.