Microservice Database Components for Resilient Heterogeneous Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems face issues of low resilience, high software development and maintenance costs, and inefficient resource utilization due to tight coupling, which limits their flexibility and adaptability in heterogeneous environments.
Innovation Solution
A microservice component-based database system architecture that decouples core components, allowing for flexible assembly and management, enabling efficient resource utilization and high availability through independent microservice components that can be dynamically deployed and managed across heterogeneous hardware platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a conventional tightly coupled database architecture is used, then the system can be implemented as a whole on specific hardware, but the system has low resilience and high software development and maintenance costs
Solution Approach 1:
The patent divides the database system into independent microservice components (parser service, optimizer service, executor service, storage engine service) that can be deployed and managed separately. This segmentation enables individual components to be replaced or updated without affecting the entire system, thereby improving resilience while maintaining manageable complexity through standardized interfaces.
Solution Approach 2:
The patent implements a dynamic architecture where microservice components can be independently deployed, scaled, and configured based on workload requirements. The system can dynamically adjust component deployment across heterogeneous hardware platforms, allowing the architecture to adapt to changing conditions without requiring complex reconfiguration of the entire system.
2Adaptability or versatility
If a tightly coupled database architecture is used, then the system can be deployed on specific hardware, but machines with different configurations have low resource utilization
Solution Approach 1:
The patent creates a universal database architecture where the same microservice components can run on different hardware platforms (x86, ARM, etc.) through standardized interfaces and a component manager that handles platform-specific details. This allows a single database system to be deployed across heterogeneous hardware configurations without requiring platform-specific versions of each component, thereby improving both adaptability and resource utilization efficiency.
Solution Approach 2:
The patent enables dynamic adjustment of system parameters such as component deployment locations, resource allocation, and configuration settings based on the specific hardware platform and workload characteristics. The component manager can modify these parameters to optimize resource utilization on different hardware configurations while maintaining the same core functionality.
3Ease of manufacture
If a tightly coupled database architecture is used, then the system can be implemented as a whole, but there are high software development, validation, and maintenance costs
Solution Approach 1:
By segmenting the database system into independent microservices with well-defined interfaces, the patent reduces the complexity of software development and maintenance. Each microservice can be developed, tested, and validated independently, reducing the overall development cost and enabling parallel work on different components without extensive coordination.
Solution Approach 2:
The patent introduces a component manager as an intermediary that handles communication and coordination between microservices. This intermediary layer simplifies the interaction between components, reducing the need for direct coupling and complex coordination logic in the microservices themselves, thereby lowering development and maintenance costs.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of this application provide a microservice component-based database system, to split a database kernel into microservice components that can be enabled and run independently and whose functions are decoupled, and implement flexible database assembly and management. The microservice component is deployed based on a system resource and a service form. The components can collaborate with each other by using a lightweight communication mechanism. A component manager provides capabilities such as registration and deregistration of a service component, component resource management, component fault tolerance, and component upgrade, to implement dynamic management of the component in a running environment. A job scheduler selects, based on a job submitted by a user, an optimal execution path including a plurality of components, and performs resource management and scheduling in a job execution process, to implement load balancing and high availability.