Database Instance Containers with Bonded Networking for Multi-Host Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems require a single hardware device for each application/database deployment, leading to an impedance mismatch between application workloads and hardware, resulting in suboptimal resource utilization and unused capacity within clusters.
Innovation Solution
Deploy database instance containers across multiple host servers, utilizing bonded network interfaces with non-overlapping IP address pools and active-active network modes to create clusters with different fault tolerances, enabling direct access to host server resources and improving system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single hardware device is used for each application/database deployment, then device reliability is improved, but resource utilization deteriorates and capacity is wasted
Solution Approach 1:
The patent segments database instances into containerized units that can be deployed across multiple host servers. Each database instance is encapsulated in a container with its own network interface, allowing independent deployment and management. This segmentation enables multiple database instances to share hardware resources while maintaining isolation and reliability.
Solution Approach 2:
The patent creates a universal container deployment framework that can host multiple different database instances on a single host server. The bonded network interface card system provides multi-functionality by supporting multiple virtual network interfaces, each capable of handling different database workloads simultaneously, thus improving resource utilization while maintaining deployment reliability.
2Productivity
If multiple database instances are deployed on a single host server, then resource utilization is improved, but network performance deteriorates due to IP address conflicts
Solution Approach 1:
The patent segments the network interface functionality by creating multiple virtual network interfaces on a single physical bonded NIC. Each virtual interface is assigned a unique IP address from non-overlapping IP pools, eliminating IP conflicts while allowing multiple database instances to operate simultaneously on the same host server with dedicated network pathways.
Solution Approach 2:
The bonded network interface card acts as an intermediary between multiple database instances and the external network. It provides network address translation and packet routing capabilities, allowing multiple IP addresses to be mapped to a single physical interface while maintaining network performance and avoiding conflicts.
3Reliability
If database instances are distributed across multiple host servers, then fault tolerance is improved, but system complexity increases
Solution Approach 1:
The patent implements self-service mechanisms through automated container orchestration that handles the complexity of distributed deployment. The system automatically manages container lifecycle, network configuration, and failover procedures across multiple host servers, reducing operational complexity while maintaining high fault tolerance through automated redundancy and load balancing.
Data Source
AI summary
Systems and methods can include one or more processing modules and one or more non-transitory storage modules storing computing instructions configured to run on the one or more processing modules and perform acts. The acts an include providing a bonded network interface on a host server, where the host server can include a plurality of internet protocol (IP) addresses. The acts also can include binding a first database instance container to a first IP address of the plurality of IP addresses of the host server such that a first database deployed inside the first database instance container has direct access to the host server. Systems and methods also can include deploying a first database instance container of a first cluster at a first host server and deploying a second database instance container of a second cluster at the first host server. Other embodiments also are disclosed herein.