Auto-starting Databases via Administrative Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud server environments, infrequently-used databases are inefficiently kept running constantly, leading to resource wastage, and there is a need for automatic start-up and shut-down mechanisms that allow clients to access databases without knowing their location or status.
Innovation Solution
Implementing an administrative database to manage auto-starting and auto-stopping of databases, using an admin DB common to each server, which handles concurrent connection requests and determines when a database is idle to initiate the auto-stop procedure, ensuring seamless transitions and error prevention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If databases are kept running constantly to ensure availability, then client access reliability is improved, but resource consumption increases
Solution Approach 1:
The database system dynamically adjusts its operational state based on usage patterns. Frequently accessed databases remain running to ensure availability, while infrequently accessed databases are automatically stopped to conserve resources. This dynamic state transition resolves the contradiction by making the system adaptable to actual usage needs rather than maintaining a static running state for all databases.
Solution Approach 2:
The system implements self-service through automated database lifecycle management. The database management system monitors access patterns and automatically starts or stops databases without manual intervention. This self-service mechanism allows the system to optimize resource allocation while maintaining availability for needed databases, eliminating the need for constant human oversight.
2Ease of operation
If manual database management is implemented, then client control over database location and status is improved, but system complexity increases
Solution Approach 1:
The system introduces an intermediary layer (database management system) that handles the complexity of database location tracking and status management. Clients interact with this intermediary through simplified interfaces, which automatically resolve database locations and manage start/stop operations. This intermediary absorbs the system complexity while presenting a simple interface to clients, resolving the contradiction between ease of operation and system complexity.
3Loss of energy
If databases are stopped when not in use to save resources, then resource efficiency is improved, but access time increases
Solution Approach 1:
The system performs preliminary actions by proactively starting databases before they are actually needed based on predicted usage patterns. The database management system analyzes historical access data and pre-loads databases that are likely to be accessed soon. This preliminary action reduces the actual access time while still allowing databases to be stopped during periods of low usage, resolving the contradiction between resource efficiency and access time.
Solution Approach 2:
The system implements periodic monitoring and evaluation of database usage patterns. Instead of continuously running all databases, the system periodically assesses which databases are frequently accessed and which are not, adjusting the running state accordingly. This periodic action allows the system to maintain high resource efficiency while ensuring that commonly accessed databases are available when needed, minimizing the impact on access time.
Data Source
AI summary
Systems and methods are presented for auto-starting and auto-stopping databases in a cloud server environment. In some embodiments, a method includes accessing, by an initial server in a network-based system, a request to connect to a target database located in a target server of the network-based system. The method can include determining, by an administrative database residing in the initial server, a location of the target database residing in the target server, switching an execution context from no database in the target server to a copy of the administrative database in the target server, performing an auto-start procedure to auto-start the target database in the target server, switching the execution context from the administrative database in the target server to the target database in the target server, and transmitting a completion acknowledgement indicating the target server is connected to the target database.