Multi-Domain Data Storage Resource Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional data storage systems face challenges in providing high performance and stability due to insufficient database connection pools, leading to difficulties in capacity expansion and personalized support for services with varying requirements.
Innovation Solution
A data storage method that involves setting multiple service domains with unique identifiers and configuring corresponding storage resources based on parameter information such as data specifications, operation and maintenance requirements, and service-level agreements (SLAs), allowing for targeted storage resource allocation for each service domain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all service lines share the same database, then resource utilization is improved, but service stability and performance cannot be guaranteed
Solution Approach 1:
The patent divides the unified database into multiple independent service domains, each with its own storage resources. This segmentation allows different service lines to have isolated storage spaces, preventing jitters in one service from affecting others, while still maintaining overall resource utilization through the shared infrastructure.
Solution Approach 2:
The patent implements personalized storage resource configuration for each service domain based on specific service requirements. Different services can have different storage capacities, access policies, and resource allocations tailored to their needs, ensuring that high-performance services receive appropriate resources while maintaining overall system efficiency.
2Quantity of substance
If database scale is expanded to cope with increased accesses, then capacity is improved, but connection pool insufficiency and maintenance difficulty increase
Solution Approach 1:
By dividing the storage system into multiple service domains with independent connection pools, the patent enables scaled capacity expansion without proportionally increasing overall system complexity. Each domain can be independently managed and scaled, reducing the burden on centralized connection pools and simplifying maintenance.
Solution Approach 2:
The patent pre-configures storage resources and connection pools for each service domain in advance, based on predicted service requirements. This preliminary allocation prevents connection pool exhaustion during peak loads and reduces the need for complex runtime resource management and dynamic scaling operations.
3Ease of operation
If traditional unified storage is used, then ease of operation is improved, but personalized support for different services cannot be provided
Solution Approach 1:
The patent creates a multi-functional storage system where a single unified architecture serves multiple service domains with different requirements. The system universally supports various service types by providing domain-specific resource configurations within the same infrastructure, maintaining operational simplicity while enabling personalized service support.
Solution Approach 2:
The patent applies different storage resource configurations and policies to different service domains based on their specific requirements. Each domain can have customized capacity, performance parameters, and access controls, allowing personalized support for diverse services while maintaining a unified system interface for ease of operation.
Data Source
AI summary
A method includes: setting at least two service domains each having a service domain identifier; configuring, based on parameter information of each of the at least two service domains, at least two storage resources corresponding to the at least two service domains; receiving a data storage request including to-be-stored data and a service domain identifier for the to-be-stored data; determining, according to the service domain identifier of the to-be-stored data, a target storage resource corresponding to the to-be-stored data from the at least two storage resources; storing the to-be-stored data to the target storage resource; receiving a data reading request carrying the service domain identifier; in response to receiving the data reading request, reading, based on the service domain identifier, the data stored at the target storage resource; and transmitting the data read from the target storage resource to a requester that sends the data reading request.