Database Server SQL Integration Reduces Lock Time
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Web systems face challenges in efficiently switching between different database management systems (DBMS) and managing modifications across various application destinations, leading to prolonged lock times and increased implementation burdens due to the need for frequent API modifications.
Innovation Solution
A database server device and server system that utilize a simple API to receive requests from a Web server, analyze and integrate SQL sentences, and execute them efficiently, reducing the load on the database server and minimizing lock times by temporarily storing and integrating SQL sentences before sending them to the DBMS.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a series of processing is divided into multiple APIs to reduce modification burden, then the burden on the DB server device is reduced, but the lock time is prolonged due to multiple HTTP communications
Solution Approach 1:
The DB server device preliminarily stores SQL sentences generated from divided API requests in a temporary storage area before executing them as a batch. This preliminary storage action allows the system to maintain divided API interfaces for ease of modification while avoiding multiple lock acquisitions, as all SQL sentences are prepared in advance and executed together in a single batch operation that acquires the lock only once.
Solution Approach 2:
The patent introduces a batch processing mechanism as an intermediary between the divided API requests and the DBMS execution. This intermediary collects multiple SQL sentences from divided requests, stores them temporarily, and then executes them as a unified batch operation. This mediator layer preserves the benefits of divided APIs while eliminating the harmful effect of prolonged lock times caused by multiple sequential executions.
2Loss of time
If a single API is used to execute a series of processing to shorten lock time, then the lock time is reduced, but the burden of implementation and modification on the DB server device increases
Solution Approach 1:
The patent segments the processing into two distinct parts: the API interface layer that receives divided requests for flexibility and ease of modification, and the execution layer that processes these requests as a unified batch operation. This segmentation allows the system to maintain simple, flexible APIs while achieving efficient single-lock execution through batch processing, thus resolving the contradiction between API simplicity and execution efficiency.
3Adaptability or versatility
If the Web system is modified for different application destinations, then it can be applied to different cases, but the API provided by the DB server device requires frequent modification which increases the burden
Solution Approach 1:
The patent creates a universal batch processing mechanism that can handle multiple different types of SQL sentences (SELECT, INSERT, UPDATE, DELETE) and various divided API request formats through a single unified execution interface. This universal batch execution layer serves multiple application destinations without requiring modifications to the core execution logic, thereby achieving high adaptability while minimizing modification burden through the use of a multi-functional batch processing system.
Data Source
AI summary
The lock time of a database upon the execution of a series of processes is decreased, and the load of the implementation/modification of the database server device upon changing the application destination of the Web system is reduced. A database server provides a prescribed simple API, and comprises a request processing unit, an SQL creation unit, and an SQL processing unit. In the database server device 120, when a plurality of divided requests are received from the Web server device as the request for requesting a series of processing, the SQL processing unit executes SQL integration processing of temporarily storing the generated SQL sentences until generation of the SQL sentences is ended for all of the plurality of divided requests, and integrating and editing the plurality of temporarily stored SQL sentences and creating the whole SQL sentence after generation of the SQL sentence is ended for all of the requests.