CN110968598A - Data request management method, system and device - Google Patents
Data request management method, system and device Download PDFInfo
- Publication number
- CN110968598A CN110968598A CN201811150642.4A CN201811150642A CN110968598A CN 110968598 A CN110968598 A CN 110968598A CN 201811150642 A CN201811150642 A CN 201811150642A CN 110968598 A CN110968598 A CN 110968598A
- Authority
- CN
- China
- Prior art keywords
- data
- request
- data request
- event
- retrieval
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 50
- 238000013507 mapping Methods 0.000 claims abstract description 37
- 238000000034 method Methods 0.000 claims description 25
- 230000003139 buffering effect Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 235000014510 cooky Nutrition 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a data request management method, which comprises the following steps: receiving a registration request of a data request event, and distributing an interface identifier for the data request event; performing database retrieval for the data request event and caching mapping relation data between the interface identifier and retrieval result data; and receiving a retrieval request of a data request event, preferentially retrieving the mapping relation data, and when corresponding data cannot be retrieved from the mapping relation data, performing database retrieval for the data request event to obtain the corresponding data. The data request event is managed and maintained in a centralized way, so that the maintenance of relevant codes at a plurality of positions of the system is avoided, the workload of developers is reduced, and the robustness of the codes is ensured. The embodiment of the invention also provides a data request management system and a data request management device.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a data request management method and a data request management system.
Background
In the field of web application, the use experience of a product user is directly influenced by the front-end and back-end data interaction mode and efficiency. The existing solution for front-end and back-end data interaction is to write the code of front-end and back-end data interaction according to business logic in an application, so that the related code is scattered in different positions of the system. Because the related codes lack unified management, developers need to repeatedly write the codes with the same functions, so that the workload of the developers is increased, later maintenance is not facilitated, and more importantly, the error probability of the codes is greatly increased.
Disclosure of Invention
Embodiments of the present invention provide a data request management method and system for managing data request events systematically, structurally, and in a flow, without maintaining relevant codes at multiple locations of the system.
According to a first aspect of the present invention, there is provided a data request management method, comprising:
receiving a registration request of a data request event, and distributing an interface identifier for the data request event;
performing database retrieval for the data request event and caching mapping relation data between the interface identifier and retrieval result data;
and receiving a retrieval request of a data request event, preferentially retrieving the mapping relation data, and when corresponding data cannot be retrieved from the mapping relation data, performing database retrieval for the data request event to obtain the corresponding data.
Preferably, a data request policy is specified in the registration request, the data request policy comprising a pre-request and a lazy request.
Preferably, for the data request event of the pre-request, the database retrieval is executed, and a piece of mapping relation data is added according to the retrieval result data.
Preferably, a unified database reconnect strategy is employed when performing database retrieval.
Preferably, the method further comprises the following steps: and maintaining related information of the data request event, wherein the related information comprises an interface identifier, an interface address, interface parameters and view interface information.
Preferably, the method further comprises the following steps: and formatting the retrieval result data before caching the mapping relation data.
Preferably, the method further comprises the following steps: and after the corresponding data are obtained, displaying the corresponding data on a WEB page.
Preferably, the method further comprises the following steps: and caching the corresponding data.
According to a second aspect of the present invention, there is provided a data request management system comprising:
the request manager is used for receiving a registration request of a data request event, distributing an interface identifier for the data request event and executing database retrieval for the data request event;
the data pool module is used for caching mapping relation data between the interface identifier and the retrieval result data;
and the WEB application module is used for preferentially searching the mapping relation data according to the searching request of the data request event, and when corresponding data cannot be searched from the mapping relation data, performing database searching for the data request event to obtain the corresponding data.
Preferably, a data request policy is specified in the registration request, the data request policy comprising a pre-request and a lazy request.
Preferably, the request manager performs database retrieval on the pre-requested data request event, and caches a piece of mapping relation data according to the retrieval result data.
Preferably, the request manager adopts a unified database reconnection strategy when performing database retrieval.
Preferably, the request manager further comprises: and maintaining related information of the data request event, wherein the related information comprises an interface identifier, an interface address, interface parameters and view interface information.
Preferably, the method further comprises the following steps: and the formatting module is used for formatting the retrieval result data before caching the mapping relation data.
Preferably, the method further comprises the following steps: and the display module is used for displaying the corresponding data on a WEB page after the corresponding data is obtained.
Preferably, the method further comprises the following steps: and the buffer module is used for buffering the corresponding data.
Preferably, the data pool module caches the mapping relationship data by using a HashMap.
According to a third aspect of the embodiments of the present invention, there is provided a computer-readable storage medium, which is characterized by storing computer instructions, and when the computer instructions are executed, the computer instructions implement the data request management method.
According to a fourth aspect of the embodiments of the present invention, there is provided a data request management apparatus including:
a memory for storing computer instructions;
a processor coupled to the memory, the processor configured to implement the data request management method described above based on execution of computer instructions stored by the memory.
One embodiment of the present invention has the following advantages or beneficial effects: the data request event is managed and maintained in a centralized way, so that the maintenance of relevant codes at a plurality of positions of the system is avoided, the workload of developers is reduced, and the robustness of the codes is ensured.
The preferred embodiments of the present invention have the following advantages or benefits: the data request events are divided into pre-request and lazy request, database retrieval is performed in advance for the pre-requested data request events, and the retrieval result data is stored in a data pool for retrieval, so that the retrieval efficiency of the system is improved.
Drawings
The above and other objects, features and advantages of the present invention will become more apparent by describing embodiments of the present invention with reference to the following drawings, in which:
FIG. 1 is a block diagram of a data request management system according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a request manager of a data request management system according to an embodiment of the invention;
FIG. 3 is a schematic structural diagram of a data request management system according to another embodiment of the present invention;
FIG. 4 is a flow chart of a data request management method according to an embodiment of the invention;
FIG. 5 is a flow chart of a data request management method according to another embodiment of the invention;
fig. 6 is a structural diagram of a data request management apparatus according to an embodiment of the present invention.
Detailed Description
The present invention will be described below based on examples, but the present invention is not limited to only these examples. In the following detailed description of the present invention, certain specific details are set forth. It will be apparent to one skilled in the art that the present invention may be practiced without these specific details. Well-known methods, procedures, and procedures have not been described in detail so as not to obscure the present invention. The figures are not necessarily drawn to scale.
Fig. 1 is a schematic structural diagram of a data request management system according to an embodiment of the present invention. The data request management system 100 includes a request manager 101, a data pool module 103, and a WEB application module 102.
When receiving a registration request of a data request event, the request manager 101 allocates an interface identifier to the data request event and stores related information of the data request event. The interface identification uniquely identifies the data request event. When the WEB application module 101 receives a plurality of registration requests, a plurality of data request events are maintained through the interface identifier. The interface code may be generated by the system in advance and then the request manager 101 assigns the interface code to a corresponding data request event when receiving a registration request. Alternatively, the request manager 101 generates a corresponding interface code for each data request event when it receives a registration request. Also, the WEB application module 101 may perform a database search in advance based on the relevant information such as the interface code, the interface parameter, and the like of the data request event after receiving the registration request, obtaining search result data.
The data pool module 103 is configured to cache mapping relationship data 104 between the interface identifier and the retrieval result data. That is, the WEB application module 101 stores the retrieved retrieval result data and the interface identification in the data pool 104.
The WEB application module 102 preferentially retrieves the mapping relationship data according to the interface identifier according to the retrieval request of the data request event, and performs database retrieval for the data request event to obtain corresponding data when corresponding data is not retrieved from the mapping relationship data.
In the embodiment of the invention, the data request events are maintained and processed in a centralized way through the request manager, each data request event applies for an interface identifier from the request manager through a registration request, and corresponding data is obtained according to the interface identifier, so that the related codes of the data request events are prevented from being maintained at a plurality of positions of the system, the workload of developers is reduced, and the robustness of the codes is ensured. Furthermore, the request manager executes database retrieval according to the relevant information of the registered event request event, and caches the retrieval result data in the data pool, so that the WEB application module can directly obtain corresponding data from the data pool, and the retrieval efficiency of the system is improved.
In some embodiments, as shown in FIG. 2, the request manager 101 provides a registration interface (register) and a retrieval interface (query) to other applications. The registration interface is used for distributing an interface identifier for the data request event. When the WEB application module sends a registration request of a data request event to the request manager, the request manager receives the registration request, acquires the relevant information of the data request event and maintains the relevant information in the request management. The related information includes, for example, interface identification, interface address, interface parameter, view interface information. When the WEB application module sends a retrieval request of a data request event, the retrieval request can be sent to the data pool module firstly, namely corresponding data is preferentially obtained from the data pool module according to the interface identifier, if the data pool module does not contain retrieval result data corresponding to the corresponding interface identifier, the retrieval request of the data request event is sent to the request manager by utilizing a retrieval interface provided by the request manager, and the request manager receives the retrieval request, executes database retrieval and returns the retrieval result data to the WEB application module.
In some embodiments, as shown in FIG. 2, the data request policy is specified when the WEB application module sends a registration request to the request manager. The data request policy includes a pre-request and a lazy request. The request manager calls a pre-retrieval method (pre query) to perform database retrieval in advance and caches retrieval result data for a pre-requested data request event, and calls a lazy retrieval method (lazy query) to perform database retrieval only when receiving a retrieval request for a lazy requested data request event.
In some embodiments, as shown in fig. 3, the data request management system 300 further includes a formatting module 106, which is located between the request manager 101 and the data pool module 103, and the formatting module 106 receives the request manager search result data, sorts the search result data according to the format specification, and stores the sorted search result data in the data pool 104. The format specification may be specified by the request manager 101 at initialization or may specify a format specification of the corresponding data required when the WEB application module sends a registration request to the request manager.
In some embodiments, as shown in FIG. 3, the data request management system 300 further includes a buffer module 105 for buffering corresponding data. For example, the corresponding data obtained by the current search of the WEB application module is cached, and the cache module can be directly read to obtain the corresponding data when the same data is accessed next time. The existing WEB data cache generally adopts a SessionStorage or a LocalStorage, and is configured according to the time needing data persistence. The data in the data buffer is synchronized to the data pool at view/page refresh. The data cache can also use Cookie to replace the SessionsStorage or LocalStorage, and the Cookie has better browser compatibility, but the Cookie space is smaller and only has 4kb, so that the data cache is not suitable for storing a large amount of data. With the updating and upgrading of browsers and the continuous development of technologies, the properties of SessionStorage and LocalStorage developed specially for storage are undoubtedly more advantageous. The data pool module may store mapping relationship data between the interface identifier and the retrieval result data using a HashMap. HashMap may also be used within the request manager to store information about data request events.
In some embodiments, the data request management system 300 further comprises a display module for displaying the corresponding data on the WEB page. The display module preferentially acquires data from the buffer module 105, and if the acquisition fails, sends a retrieval request to the data pool module to acquire corresponding data.
It should be noted that the request manager, the formatting module and the data pool module may all exist as global objects in the system operation. In the system starting stage, global objects of a request manager, a formatting module and a data pool module are respectively created, and in the following data interaction process, a method in the object is called to complete corresponding functions. The data request management system is particularly suitable for single-page applications and hybrid mobile applications. A single page Web application (SPA), an application that has only one Web page, is a Web application that loads a single HTML page and dynamically updates the page as the user interacts with the application. The hybrid mobile application is an application between a Web-App and a Native-App, and has the advantages of good user interaction experience of the Native App and cross-platform development of the Web App.
Fig. 4 is a flowchart of a data request management method according to an embodiment of the present invention. The method specifically comprises the following steps.
In step S401, a registration request of a data request event is received, and an interface identifier is allocated to the data request event.
In step S402, database retrieval is performed for the data request event, and mapping relationship data between the interface identification and the retrieval result data is cached.
In step S403, a retrieval request of the data request event is received, the mapping relationship data is preferentially retrieved, and when the corresponding data is not retrieved from the mapping relationship data, database retrieval is performed for the data request event to obtain the corresponding data.
In the embodiment of the invention, data request events are maintained and managed in a centralized way, for each data request event, an interface identifier is applied through a registration request, and then corresponding data is obtained according to the interface identifier, so that the related codes of the data request events are prevented from being maintained at a plurality of positions of the system. For registered event request events, database retrieval can be performed before retrieval requests, retrieval result data is cached in the data pools, and corresponding data is obtained from the data pools after the retrieval requests are received, so that the retrieval efficiency of the system is improved.
Fig. 5 is a flowchart of a data request management method according to another embodiment of the present invention, which specifically includes the following steps.
In step S501, a registration request of a data request event is received, an interface identifier is allocated to the data request event, and a request policy is specified.
In step S502, a request policy is determined. When the request policy is a pre-request, step S503 is performed, and when the request policy is a lazy request, step S505 is performed.
In step S503, database retrieval is performed for the data request event, and mapping relationship data between the interface identification and the retrieval result data is cached.
In step S504, a retrieval request of the data request event is received, and the mapping relationship data is retrieved to obtain corresponding data.
In step S505, a retrieval request of the data request event is received, and database retrieval is performed to obtain corresponding data.
In step S506, the retrieved corresponding data is cached.
In step S507, the corresponding data is displayed on the WEB page.
In the embodiment of the invention, for each data request event, a request strategy can be designated when a registration request is received, for the data request event requested in advance, the system carries out database retrieval in advance, the obtained retrieval result data is stored in a data pool for retrieval, for the request strategy requested in a lazy way, the database retrieval is carried out when a retrieval request is received, and the retrieval efficiency of the system can be improved through the pre-request. Further, the retrieved corresponding data is cached in the cache and displayed on the WEB page. The data in the buffer and the data in the data pool can be synchronized in real time according to the interface identification.
Fig. 6 is a structural diagram of a data request management apparatus according to an embodiment of the present invention. The apparatus shown in fig. 6 is only an example and should not limit the functionality and scope of use of embodiments of the present invention in any way.
Referring to fig. 6, the apparatus includes a processor 601, a memory 602, and an input-output device 603 connected by a bus. The memory 602 includes a Read Only Memory (ROM) and a Random Access Memory (RAM), and various computer instructions and data required to perform system functions are stored in the memory 602 and read by the processor 601 from the memory 602 to perform various appropriate actions and processes. An input/output device including an input portion of a keyboard, a mouse, and the like; an output section including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section including a hard disk and the like; and a communication section including a network interface card such as a LAN card, a modem, or the like. The memory 602 also stores the following computer instructions to perform the operations specified by the apparatus of an embodiment of the present invention: receiving a registration request of a data request event, and distributing an interface identifier for the data request event; performing database retrieval for the data request event and caching mapping relation data between the interface identifier and retrieval result data; and receiving a retrieval request of a data request event, preferentially retrieving the mapping relation data, and when corresponding data cannot be retrieved from the mapping relation data, performing database retrieval for the data request event to obtain the corresponding data.
Accordingly, embodiments of the present invention provide a computer-readable storage medium storing computer instructions that, when executed, implement the operations specified by the above-described method.
The flowcharts and block diagrams in the figures and block diagrams illustrate the possible architectures, functions, and operations of the systems, methods, and apparatuses according to the embodiments of the present invention, and may represent a module, a program segment, or merely a code segment, which is an executable instruction for implementing a specified logical function. It should also be noted that the executable instructions that implement the specified logical functions may be recombined to create new modules and program segments. The blocks of the drawings, and the order of the blocks, are thus provided to better illustrate the processes and steps of the embodiments and should not be taken as limiting the invention itself.
The various modules or units of the system may be implemented in hardware, firmware or software. The software includes, for example, a code program formed using various programming languages such as JAVA, C/C + +/C #, SQL, and the like. Although the steps and sequence of steps of the embodiments of the present invention are presented in method and method diagrams, the executable instructions of the steps implementing the specified logical functions may be re-combined to create new steps. The sequence of the steps should not be limited to the sequence of the steps in the method and the method illustrations, and can be modified at any time according to the functional requirements. Such as by performing certain steps of the features in parallel or in reverse order.
Systems and methods according to the present invention may be deployed on a single server or on multiple servers. For example, different modules may be deployed on different servers, respectively, to form a dedicated server. Alternatively, the same functional unit, module or system may be deployed in a distributed fashion across multiple servers to relieve load stress. The server includes but is not limited to a plurality of PCs, PC servers, blades, supercomputers, etc. on the same local area network and connected via the Internet.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (19)
1. A data request management method, comprising:
receiving a registration request of a data request event, and distributing an interface identifier for the data request event;
performing database retrieval for the data request event and caching mapping relation data between the interface identifier and retrieval result data;
and receiving a retrieval request of a data request event, preferentially retrieving the mapping relation data, and when corresponding data cannot be retrieved from the mapping relation data, performing database retrieval for the data request event to obtain the corresponding data.
2. The data request management method according to claim 1, wherein a data request policy is specified in the registration request, the data request policy including a pre-request and a lazy request.
3. The data request management method according to claim 2, wherein, for the data request event of the pre-request, database search is performed, and a piece of mapping relation data is added according to the search result data.
4. The data request management method of claim 1, wherein a unified database reconnect policy is employed when performing database retrieval.
5. The data request management method of claim 1, further comprising: and maintaining related information of the data request event, wherein the related information comprises an interface identifier, an interface address, interface parameters and view interface information.
6. The data request management method of claim 1, further comprising: and formatting the retrieval result data before caching the mapping relation data.
7. The data request management method of claim 1, further comprising: and after the corresponding data are obtained, displaying the corresponding data on a WEB page.
8. The data request management method of claim 7, further comprising: and caching the corresponding data.
9. A data request management system, comprising:
the request manager is used for receiving a registration request of a data request event, distributing an interface identifier for the data request event and executing database retrieval for the data request event;
the data pool module is used for caching mapping relation data between the interface identifier and the retrieval result data;
and the WEB application module is used for preferentially searching the mapping relation data according to the searching request of the data request event, and when corresponding data cannot be searched from the mapping relation data, performing database searching for the data request event to obtain the corresponding data.
10. The data request management system of claim 9, wherein a data request policy is specified in the registration request, the data request policy comprising pre-request and lazy request.
11. The data request management system according to claim 9, wherein the request manager performs database retrieval for the pre-requested data request event and caches a piece of mapping relation data according to the retrieval result data.
12. The data request management system of claim 9, wherein the request manager employs a unified database reconnect policy when performing database retrieval.
13. The data request management system of claim 9, wherein the request manager further comprises: and maintaining related information of the data request event, wherein the related information comprises an interface identifier, an interface address, interface parameters and view interface information.
14. The data request management system of claim 9, further comprising: and the formatting module is used for formatting the retrieval result data before caching the mapping relation data.
15. The data request management system of claim 9, further comprising: and the display module is used for displaying the corresponding data on a WEB page after the corresponding data is obtained.
16. The data request management system of claim 9, further comprising: and the buffer module is used for buffering the corresponding data.
17. The data request management system of claim 9, wherein the data pool module employs a HashMap to cache the mapping relationship data.
18. A computer-readable storage medium storing computer instructions which, when executed, implement a data request management method as claimed in any one of claims 1 to 8.
19. A data request management apparatus, comprising:
a memory for storing computer instructions;
a processor coupled to the memory, the processor configured to perform a method of implementing data request management as claimed in any one of claims 1 to 8 based on computer instructions stored by the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811150642.4A CN110968598A (en) | 2018-09-29 | 2018-09-29 | Data request management method, system and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811150642.4A CN110968598A (en) | 2018-09-29 | 2018-09-29 | Data request management method, system and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110968598A true CN110968598A (en) | 2020-04-07 |
Family
ID=70027553
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811150642.4A Pending CN110968598A (en) | 2018-09-29 | 2018-09-29 | Data request management method, system and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110968598A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120117105A1 (en) * | 2010-11-05 | 2012-05-10 | Apple Inc. | Collaborative Database Operations |
| CN103020208A (en) * | 2012-12-06 | 2013-04-03 | 百度在线网络技术（北京）有限公司 | Searching method and device adapting to mobile terminal |
| CN103336849A (en) * | 2013-07-24 | 2013-10-02 | 昆明理工大学 | Method and device for increasing retrieval speed in database retrieval system |
| CN103455865A (en) * | 2012-06-01 | 2013-12-18 | 成都勤智数码科技股份有限公司 | Achieving method for integrated operation and maintenance |
| CN103678381A (en) * | 2012-09-17 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Caption processing method, device and system |
| CN105930428A (en) * | 2010-12-20 | 2016-09-07 | 销售力网络公司 | Methods and systems for performing cross store joins in a multi-tenant store |
-
2018
- 2018-09-29 CN CN201811150642.4A patent/CN110968598A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120117105A1 (en) * | 2010-11-05 | 2012-05-10 | Apple Inc. | Collaborative Database Operations |
| CN105930428A (en) * | 2010-12-20 | 2016-09-07 | 销售力网络公司 | Methods and systems for performing cross store joins in a multi-tenant store |
| CN103455865A (en) * | 2012-06-01 | 2013-12-18 | 成都勤智数码科技股份有限公司 | Achieving method for integrated operation and maintenance |
| CN103678381A (en) * | 2012-09-17 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Caption processing method, device and system |
| CN103020208A (en) * | 2012-12-06 | 2013-04-03 | 百度在线网络技术（北京）有限公司 | Searching method and device adapting to mobile terminal |
| CN103336849A (en) * | 2013-07-24 | 2013-10-02 | 昆明理工大学 | Method and device for increasing retrieval speed in database retrieval system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11882054B2 (en) | Terminating data server nodes | |
| CN109933585B (en) | Data query method and data query system | |
| CN108009008B (en) | Data processing method and system and electronic equipment | |
| US20190311008A1 (en) | Linked data processor for database storage | |
| WO2021174928A1 (en) | Page pre-rendering method and apparatus, electronic device, and storage medium | |
| US20120047107A1 (en) | System and method for implementing on demand cloud database | |
| CN111897638B (en) | Distributed task scheduling method and system | |
| CN107038222B (en) | Database cache implementation method and system | |
| KR20110052714A (en) | Provisioning virtual resources using name resolution | |
| CN107958018B (en) | Method and device for updating data in cache and computer readable medium | |
| US20160098462A1 (en) | Enterprise Reporting Capabilities In Storage Management Systems | |
| CN111666293A (en) | Database access method and device | |
| CN111400350B (en) | Configuration data reading method, system, electronic device and storage medium | |
| US10747773B2 (en) | Database management system, computer, and database management method | |
| CN115640110A (en) | Distributed cloud computing system scheduling method and device | |
| US10698637B2 (en) | Stale block resynchronization in NVM based systems | |
| US20210149870A1 (en) | Method, apparatus, and computer program product for improved tracking of state data | |
| US10452613B2 (en) | Persistent directory for variable-size entry container free-space handling | |
| CN111124482B (en) | Configuration method and device for document information | |
| CN110968598A (en) | Data request management method, system and device | |
| CN115469866A (en) | Page rendering method and device of applet, electronic device and storage medium | |
| CN103677949A (en) | Method and device for caching entity with variable unique value | |
| US7383387B2 (en) | Document transformation tool | |
| CN113157722A (en) | Data processing method, device, server, system and storage medium | |
| US11748203B2 (en) | Multi-role application orchestration in a distributed storage system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |