Dynamic data service system, method, program product, storage medium, and apparatus
The dynamic data service system enables dynamic configuration of data sources and APIs, solving the problem of redeploying existing systems, improving system flexibility and responsiveness, and reducing communication costs during development and deployment.
Patent Information
- Application Number
- CN202511104587.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-07
- Publication Date
- 2025-11-21
AI Technical Summary
The existing system uses a static data source configuration method, which requires redeployment every time a new data source is added or an API interface is expanded, making it unable to respond to business needs in real time.
A dynamic data service system is adopted, which realizes the dynamic configuration of data sources and APIs through a web configuration center and API query service module. This includes visual interface management, connection testing, persistence, dynamic hot updates and event-driven architecture, and uses Redis message middleware for communication and memory updates.
Business personnel can independently complete the data source and API configuration, while R&D personnel only need to maintain the underlying framework, reducing communication costs, enabling rapid deployment, and providing flexible data services.
Smart Images
Figure CN120994731A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of computer application technology, and more specifically, to a dynamic data service system, method, program product, storage medium, and apparatus. Background Technology
[0002] The existing system uses a static data source configuration approach, configuring the data source through hard coding and then providing a fixed Application Programming Interface (API) for callers to use. However, every time a new data source is added or the API interface is expanded, redeployment is required before it can be used after development and deployment. Summary of the Invention
[0003] This disclosure provides a dynamic data service system, method, program product, storage medium, and apparatus that enables dynamic configuration of data sources and APIs.
[0004] On one hand, embodiments of this disclosure relate to a dynamic data service system, which includes a web configuration center and an API query (API_Query) service module.
[0005] The Web configuration center includes: a visual configuration submodule, which provides a visual interface to receive user operations on data sources and APIs, including at least one of the following: adding, deleting, modifying, or querying; a data source management submodule, which receives user confirmation of the data source to be operated on through the visual interface, performs connection tests on the data source, and persists the data to a local database after a successful connection test; an API management submodule, which receives user selection of the data source for the API through the visual interface, and persists the SQL (Structured Query Language) written for the API to a local database after a successful test; and a publishing submodule, which publishes the user-specified operation type, the object to be changed, and the unique identifier of the object to be changed to a specified channel of the message middleware.
[0006] The API query service module includes: an event listening submodule, used to listen for publications of the Web configuration center based on the message middleware; a data source preheating submodule, used to perform preheating initialization when the system starts; a dynamic hot update submodule, used to dynamically update the local cache when the event listening submodule detects a change event; and an interface management submodule, used to receive requests from callers through a unified RESTful interface, automatically match the corresponding data source and SQL logic, and return it to the caller. The preheating initialization includes: loading the configuration of all published data sources, initializing the connection pool corresponding to the data source, caching the data source ID (identification identifier) and connection pool reference in local memory; loading the configuration of all published APIs, precompiling the corresponding SQL templates for each API, binding the data source with the API's unique identifier, and caching it in local memory.
[0007] In some implementations, the dynamic hot update submodule is configured to: when the change event is adding a new data source, initialize the data source connection pool and add the new data source to local memory; when the change event is modifying a data source, close the old data source connection pool and then initialize the modified new data source and add it to local memory; when the change event is deleting a data source, clear the local memory and connection pool corresponding to the data source; when the change event is adding an API, precompile the SQL template corresponding to the new API, initialize and cache it in local memory; when the change event is modifying an API, first delete the local cache of the API, precompile the SQL template corresponding to the modified API, initialize and cache it in local memory.
[0008] In some implementations, when the change event is a modification of the data source, existing requests are allowed to continue to be served during the update operation, and the old connection pool is replaced after the new connection pool is initialized.
[0009] In some implementations, the interface management submodule is configured to: parse the request to obtain parameters for each field in the request, including group, API name, and version; query the unique identifiers of the API and data source based on the parameters; obtain the corresponding SQL based on the unique identifiers of the API and data source; execute the obtained SQL and return the execution result to the caller.
[0010] In some implementations, the message middleware includes a remote dictionary server (Redis).
[0011] In some implementations, the Web configuration center also includes a permission management submodule, which is used to manage APIs by business group to achieve permission isolation and resource allocation.
[0012] On the other hand, embodiments of this disclosure relate to a method for providing dynamic data services, which operates based on the system described in any embodiment of this disclosure, including: receiving user configurations of data source connection parameters and API SQL templates, version numbers, and permission groups through a visual interface of a Web configuration center; publishing configuration change events to a message middleware when configuration changes occur; listening to the message middleware through an API query service, and dynamically updating the data source connection pool and / or the pre-compiled SQL template corresponding to the API in local memory according to the configuration change events; receiving a request from a caller through the API query service, parsing the parameters of the request and matching the pre-compiled SQL template with the data source; the API query service executing the pre-compiled SQL template to execute SQL, querying the corresponding data source, and returning the query results to the requester.
[0013] In some implementations, dynamically updating the data source connection pool and / or the pre-compiled SQL template corresponding to the API in local memory according to the configuration change event includes: when the change event is adding a data source, initializing the data source connection pool and adding the new data source to local memory; when the change event is modifying a data source, closing the old data source connection pool and then initializing the modified new data source and adding it to local memory; when the change event is deleting a data source, clearing the local memory and connection pool corresponding to the data source; when the change event is adding an API, pre-compiling the SQL template corresponding to the new API, initializing and caching it in local memory; when the change event is modifying an API, first deleting the local cache of the API, pre-compiling the SQL template corresponding to the modified API, initializing and caching it in local memory.
[0014] Furthermore, embodiments of this disclosure also relate to a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any embodiment of this disclosure.
[0015] Embodiments of this disclosure also relate to a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in any embodiment of this disclosure.
[0016] In addition, embodiments of this disclosure also relate to a computer device, comprising: a memory storing a computer program thereon; a processor executing the computer program to implement the steps of the method described in any embodiment of this disclosure; and a display for displaying a visual interface.
[0017] According to the embodiments described in this disclosure, the present invention has the following superior effects:
[0018] Using the system of this invention, business personnel can independently complete the configuration and release of data sources and APIs, while R&D personnel only need to maintain the underlying framework.
[0019] It uses a standard RESTful interface to receive requests from callers, making it easy to use, user-friendly, and allowing for rapid deployment while reducing communication costs.
[0020] Various aspects, features, advantages, etc., of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. These aspects, features, advantages, etc., will become clearer from the following detailed description with reference to the accompanying drawings. Attached Figure Description
[0021] Figure 1 This is a block diagram of a dynamic data service system according to an exemplary embodiment of this disclosure.
[0022] Figure 2 This is a block diagram of a Web configuration center according to an exemplary embodiment of this disclosure.
[0023] Figure 3 This is a block diagram of an API query service module according to an exemplary embodiment of this disclosure.
[0024] Figure 4 This is a flowchart of a method for providing dynamic data services according to an exemplary embodiment of this disclosure.
[0025] Figure 5 This is an exemplary implementation of the interactive process for providing dynamic data services.
[0026] Figure 6 This is a block diagram of a computer device according to an exemplary embodiment of the present disclosure. Detailed Implementation
[0027] This disclosure will describe exemplary embodiments of the invention in more detail with reference to the accompanying drawings. It should be noted that the invention can have various embodiments and is not limited to the specific embodiments described herein or shown in the drawings.
[0028] The terms “comprising,” “including,” and “having” are used herein to indicate the presence of certain features, steps, operations, elements, and / or components, but do not exclude the presence or addition of other features, steps, operations, elements, components, or combinations thereof. Unless explicitly defined by context, the terms “first,” “second,” and similar terms do not indicate any priority or order, but are used only to distinguish different elements in the description.
[0029] This invention provides a dynamic data service system, method, program product, storage medium, and device. The system includes: a Web configuration center, which provides a visual interface to manage the lifecycle of data sources, configure and version the API interface, and manage permission groups. The Web configuration center allows users to configure data sources, SQL templates, request / return parameter mapping relationships, and interface version numbers through the interface, and configuration changes take effect in real time; and an API query service module, which provides a standard RESTful query interface based on the configuration information of the Web configuration center, listens for configuration change information based on an event-driven architecture, and dynamically updates the local cache. The Web configuration center publishes data source or API change events through Redis, and the API query service module, as a subscriber, receives the events and completes the corresponding local memory updates.
[0030] Figure 1 The modular architecture of a dynamic data service system according to an exemplary embodiment of the present invention is shown. For example... Figure 1 As shown, the dynamic data service system 110 may include a Web configuration center 111 and an API query service module 112, which are interconnected. In some implementations, the dynamic data service system 110 adopts a microservice architecture. Both the Web configuration center 111 and the API query service module 112 are deployed using Docker containerization technology and registered with a microservice registry (Eureka) for service discovery and governance. For example, the backend (API query service module 112) is mainly built on Java 1.8 and the Spring Cloud microservice framework, and provides services externally through Spring Cloud Gateway as a unified gateway entry point. The frontend (Web configuration center 111) uses React to build the visual interface of the Web configuration center.
[0031] In some implementations, such as Figure 2 As shown, the Web configuration center 111 includes a visual configuration submodule 201, a data source management submodule 202, an API management submodule 203, a publishing submodule 205, etc.
[0032] The visual configuration submodule 201 provides a visual interface to receive user operations on data sources and APIs, including at least one of the following: adding, deleting, modifying, or querying. For example, a system administrator can create users and assign them to business groups. Users log into the Web configuration center and can perform operations such as adding, modifying, and deleting data sources on the data source management page.
[0033] The data source management submodule 202 is used to receive user confirmation of the data source to be operated on through the visual interface, perform a connection test on the data source, and persist the data to the local database 204 after the connection test is successful. For example, on the data source management page, when the user clicks "confirm," the background will perform a connection test on the data source. If the test is successful, the data source will be persisted to the local database 204.
[0034] The API management submodule 203 is used to receive the data source selected by the user for the API through the visual interface, and persist the SQL written for the API to the local database 204 after a successful test. For example, on the API management page (the API includes the user's group information, API name, and version number), the user first selects a data source and writes SQL for that data source (e.g., using an SQL template), then tests the written SQL, and persists it to the local database 204 after a successful test. In some implementations, the SQL is used to query the corresponding data source.
[0035] The publishing submodule 205 is used to publish the user-specified operation type, the object to be changed, and the unique identifier of the object to be changed, received through the visual interface, to a specified channel of the message middleware. In some embodiments, the message middleware includes Redis. That is, the Web configuration center 111 and the API query service module 112 communicate based on an event-driven architecture (Redis Pub / Sub). The Web configuration center 111, as a publisher (Pub), publishes change events of data sources or APIs through Redis, and the API query service module 112, as a subscriber (Sub), receives the events and completes the corresponding local memory update. The functional modules of the API query service module 112 are described below.
[0036] In some implementations, such as Figure 3 As shown, the API query service module 112 includes: an event listening submodule 301, a data source preheating submodule 302, a dynamic hot update submodule 303, an interface management submodule 305, etc.
[0037] The event listening submodule 301 is used to listen for the publication of the Web configuration center 111 based on the message middleware (e.g., event-driven architecture (Redis Pub / Sub)), including the publication of change events to the data source or API.
[0038] The data source preheating submodule 302 is used to perform preheating initialization when the system starts. The preheating initialization includes: loading the configuration of all published data sources, initializing the connection pool corresponding to each data source, and caching the data source ID and connection pool reference to local memory 304; loading the configuration of all published APIs, precompiling the corresponding SQL templates for each API and caching them to local memory 305, and binding the data source with the corresponding API unique identifier.
[0039] The dynamic hot update submodule 303 is used to dynamically update the local cache when the event listening submodule detects a change event.
[0040] In some implementations, the dynamic hot update submodule 303 is configured to: initialize the data source connection pool and add the new data source to local memory 304 when the change event is a new data source; close the old data source connection pool and then initialize the modified new data source and add it to local memory 304 when the change event is a modified data source; clear the local memory and connection pool corresponding to the data source when the change event is a deleted data source; precompile the SQL template corresponding to the new API, initialize and cache it in local memory 304 when the change event is a modified API; first delete the local cache of the API, precompile the SQL template corresponding to the modified API, initialize and cache it in local memory 304 when the change event is a modified API. In some implementations, when the change event is a modified data source, during the update operation, existing requests are allowed to continue to be served, and the old connection pool is replaced after the new connection pool is initialized, completing a seamless switchover.
[0041] The interface management submodule 305 is used to receive requests from the caller (or the caller) through a unified RESTful interface, automatically match the corresponding data source and SQL logic, and return the results to the caller. In some implementations, the interface management submodule 305 is configured to: parse the request to obtain parameters for the group, API name, and version fields in the request; query the unique identifiers of the API and data source based on the parameters; obtain the corresponding SQL based on the unique identifiers of the API and data source; execute the obtained SQL and return the execution result to the caller. In some implementations, the external caller accesses the API_Query instance through the RESTful interface (access path: / api / {group} / {apiName} / {version} / ), which is routed through the gateway. The API_Query resolves the route, then queries the configuration center to find the API to be executed and the unique identifier of the data source, then retrieves the corresponding reference from local memory 304, executes the SQL, and returns the result to the caller.
[0042] In some implementations, the Web configuration center 111 also includes a permission management submodule (not shown) for managing APIs by business group, thereby achieving permission isolation and resource allocation.
[0043] In some implementations, the API_Query service (API query service module 112) supports a pluggable data source adaptation mechanism, which can dynamically load and unload different types of data source adapters, including MySQL, Doris, TiDB, etc.
[0044] In some implementations, the API_Query service further includes: a parameter validation module for validating the type and range of request parameters; a response format specification module for encapsulating the query results into a response format conforming to the JSON Schema standard; and a circuit breaker mechanism module for handling high-concurrency or abnormal request scenarios to ensure system stability.
[0045] In some implementations, the dynamic data service system 110 may integrate a Prometheus module to monitor the frequency of configuration changes and the success rate of API calls.
[0046] In some implementations, by streamlining the business logic, data source adaptation, dynamic loading, and dynamic unloading can be abstracted into reusable components so that they can be reused in applications, thereby reducing development costs.
[0047] Based on the foregoing description of the present invention, it should be understood that the present invention can also be implemented as a method. Therefore, embodiments of this disclosure relate to a method for providing dynamic data services, based on the system described in any embodiment of this disclosure.
[0048] like Figure 4 As shown, the method may include: S10, receiving user configurations for data source connection parameters and API SQL templates, version numbers, and permission groups through the visual interface of the Web configuration center; S20, publishing configuration change events to the message middleware when configuration changes occur; S30, listening to the message middleware through the API query service (API_Query), and dynamically updating the data source connection pool and / or the pre-compiled SQL template corresponding to the API in local memory according to the configuration change events; S40, receiving a request from the caller through the API query service, parsing the parameters of the request, and matching the pre-compiled SQL template with the data source; S50, the API query service executes the SQL using the pre-compiled SQL template, queries the corresponding data source, and returns the query results to the requester.
[0049] In some implementations, in S30, dynamically updating the data source connection pool and / or the pre-compiled SQL template corresponding to the API in local memory according to the configuration change event includes: when the change event is adding a data source, initializing the data source connection pool and adding the new data source to local memory; when the change event is modifying a data source, closing the old data source connection pool and then initializing the modified new data source and adding it to local memory; when the change event is deleting a data source, clearing the local memory and connection pool corresponding to the data source; when the change event is adding an API, pre-compiling the SQL template corresponding to the new API, initializing and caching it in local memory; when the change event is modifying an API, first deleting the local cache of the API, pre-compiling the SQL template corresponding to the modified API, initializing and caching it in local memory.
[0050] In the example, such as Figure 5 As shown, users log in to the Web Configuration Center to perform CRUD operations on the data source and API. The Web Configuration Center then publishes messages via Redis. After receiving a message, API_Query retrieves the latest information (including the latest data source and / or API configuration) from the Web Configuration Center using a unique identifier (database primary key), initializes it, and updates its local memory. Callers invoke the API_Query service through the API configured in the Web Configuration Center. The API_Query service executes the specific SQL and returns the results to the caller.
[0051] As can be seen from the various embodiments in this disclosure, the present invention flexibly configures data sources or APIs through a Web configuration center and API query service module, which can address the problems of insufficient flexibility in existing systems, the need to redeploy data sources when they change or add new API interface services, and the inability to respond to business needs in real time.
[0052] It should be understood that the methods, steps, processes, operations, etc., described in the various embodiments of this disclosure can be implemented by computer software. Therefore, embodiments of this disclosure also relate to a computer program product, which includes a computer program, wherein the computer program, when executed by a processor, implements the steps (processes, operations, etc.) of the methods described in any embodiment of this disclosure.
[0053] Furthermore, it should be understood that the computer program product of the embodiments of this disclosure can be stored on a computer-readable storage medium. Therefore, embodiments of this disclosure also relate to a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps (processing, operations, etc.) of the method described in any embodiment of this disclosure. In some embodiments, the computer-readable storage medium includes, for example, hard disks, floppy disks, magnetic tapes, optical disks, solid-state drives, flash memory, etc.
[0054] Furthermore, it can be understood that the computer program of the embodiments of this disclosure can be executed by a computer device. Therefore, embodiments of this disclosure also relate to a computer device comprising: a memory storing a computer program thereon; and a processor that, when executing the computer program, implements the steps (processing, operations, etc.) of the method described in any embodiment of this disclosure.
[0055] Figure 6 An exemplary structure of a computer device is shown. Figure 6 As shown, the computer device 100 may include at least a processor 101 and a memory 102, wherein the memory 102 may be or include a storage medium storing a computer program (or computer-readable instructions) thereon, and the processor 101 executes the computer program to perform some or all of the operations described in any embodiment of the present disclosure.
[0056] In some embodiments, the computer device 100 may further include a data storage device 103, a display 104, a speaker 105, and a communication module 106. The processor 101, memory 102, and data storage device 103 communicate with each other via a bus and interact with peripheral devices, such as the display 104 and communication module 106, via the bus and I / O module 107.
[0057] Specifically, data storage device 103 can store application programs and their various configuration files and data. Computer programs are stored on memory 102. Processor 101 executes the computer programs to perform various processes, operations, or steps of the dynamic data service system, or to execute various steps of a method for providing dynamic data services. Display 104 can be used to display a visual configuration interface.
[0058] In optional embodiments, the communication module 106 may be omitted where communication with the other systems, devices, or equipment is not required. In some embodiments, the computer device 100 may further include a speaker 105 for voice output.
[0059] In some implementations, processor 101 may include any suitable semiconductor-based electronic processing unit, chip, microchip, or integrated circuit (IC). Memory 102 is a programmable memory, which may include any suitable electronic storage device configured to store instructions and be reprogrammable. For example, programmable memory may include an erasable programmable read-only memory (EPROM) device. Data storage device 103 may be a persistent storage device, which may include any suitable electronic storage configured to retain stored information as power cycles. For example, data storage device 103 may include a hard disk drive, solid-state drive (SSD), flash memory drive, hybrid drive, etc., or any combination thereof.
[0060] Therefore, processor 101 can control the output of information on I / O module 107 by storing information in memory and / or executing programs / instructions stored in memory. For example, several aspects of the methods described herein can be executed by processor 101 according to programs / instructions stored in memory (e.g., memory 102 and / or data storage device 103).
[0061] Furthermore, the processor 101 can electronically communicate with the I / O module 107 and / or the communication module 106 to receive or send relevant instructions and information. The I / O module 107 may include any suitable mechanical or virtual user interface configured to enable a user to interact with the computer device 100 or to allow the user to perform one or more functions of the computer device 100 itself, such as a graphical user interface (GUI) on a screen or other display. In some instances, the user interface may include a voice interface capable of speech recognition, through which an operator can provide voice commands to the processor.
[0062] The communication module 106 may include any suitable devices and / or structures configured to facilitate information exchange between the computer device 100 and external electronic devices. The communication module 106 may include devices configured to send and / or receive wireless or wired information with other devices. For example, the communication module 106 may include an antenna, a transceiver, a connector for wired reception and / or transmission of data, a data exchange device, etc., or any combination thereof. The communication module 106 may also include ancillary components, such as filtering circuits, encryption / decryption circuits, and / or integrated circuit (IC) chips for processing signals (e.g., (Chip). In some implementations, the communication module 106 may include a WiFi device configured to connect to a local wireless network.
[0063] In some embodiments, computer device 100 may include smartphones, wearable computers, portable / mobile electronic devices, tablet computers, smartwatches, personal digital assistants (PDAs), personal computers (PCs), desktop computers, laptop computers, servers, and so on. Computer device 100 may include or have installed one or more application programs (APPs), one of which is configured to perform the dynamic data service system and methods described herein.
[0064] Although not shown, it should be understood that the computer device 100 also includes a power supply component, which may include any suitable device and / or structure configured to provide an electrical interface between the computer device 100 and a power source. The power source may include any suitable source of electrical energy, such as a battery, socket, capacitor, fuel cell, etc., or any combination thereof. Additionally or optionally, the power source may be included within the power supply component. For example, a battery or battery pack may be included within the computer device 100. In some embodiments, the battery may be rechargeable, for example, charged via a cable or an interface provided by the power supply component. In some embodiments, the power supply component may share features with or repeat features of the communication module 106. For example, a USB or micro-USB cable connector may be included in the computer device 100, so that power supply or data communication is performed by the same component.
[0065] Those skilled in the art should understand that the above disclosure is merely illustrative of embodiments of this disclosure, and the scope of patent protection claimed in this application is not limited thereto. Various modifications, alterations, substitutions, and other changes can be made to the embodiments disclosed herein without departing from the spirit and essence of this disclosure, and such changes are within the scope covered by the claims of this application. For example, one or more processes described in the system implementation may be incorporated as steps into the method implementation, or one or more steps in the method implementation may be used as module functions or module-executed processes in the system implementation.
Claims
1. A dynamic data service system, characterized in that, This includes a web configuration center and an API query service module; The Web configuration center includes: The visual configuration submodule is used to provide a visual interface to receive user operations on the data source and the API, and the operations include at least one of the following: adding, deleting, modifying, and querying. The data source management submodule is used to receive confirmation from the user about the data source to be operated through the visual interface, perform connection tests on the data source, and persist the data to the local database after the connection test is successful. The API management submodule is used to receive the data source selected by the user for the API through the visual interface, and persist it to the local database after the SQL test written for the API is successful. The publishing submodule is used to publish the user-specified operation type, the object to be changed, and the unique identifier of the object to be changed, received through the visual interface, to a specified channel of the message middleware. The API query service module includes: The event listening submodule is used to listen for publications in the Web configuration center based on the message middleware; The data source preheating submodule is used to perform preheating initialization when the system starts. The preheating initialization includes: loading the configuration of the published data source, initializing the connection pool corresponding to the data source, and caching the data source ID and connection pool reference in local memory; loading the configuration of the published API, precompiling the corresponding SQL template for each API, and binding the data source with the API's unique identifier and caching it in local memory. The dynamic hot update submodule is used to dynamically update the local cache when the event listening submodule detects a change event; The interface management submodule is used to receive requests from callers through a unified RESTful interface, automatically match the corresponding data source and SQL logic, and return them to the caller.
2. The system according to claim 1, characterized in that, The dynamic hot update submodule is configured as follows: When the change event is a new data source, initialize the data source connection pool and add the new data source to local memory; When the change event is a modification of the data source, the old data source connection pool is closed, and then the modified new data source is initialized and added to local memory; When the change event is a data source deletion, clear the local memory and connection pool corresponding to that data source. When the change event is a new API, the SQL template corresponding to the new API is pre-compiled, initialized, and cached in local memory; When the change event is an API modification, first delete the local cache of the API, precompile the SQL template corresponding to the modified API, initialize and cache it in local memory.
3. The system according to claim 2, characterized in that, When the change event is a modification of the data source, existing requests are allowed to continue to be served during the update operation, and the old connection pool will be replaced after the new connection pool is initialized.
4. The system according to claim 1, characterized in that... The interface management submodule is configured as follows: Parse the request to obtain the parameters of the group, API name, and version fields in the request; Based on the parameters, query the API and the unique identifier of the data source; Retrieve the corresponding SQL based on the API and the unique identifier of the data source; Execute the obtained SQL and return the execution result to the caller.
5. The system according to claim 1, characterized in that, The message middleware includes the remote dictionary service Redis.
6. The system according to claim 1, characterized in that, The Web configuration center also includes: The permissions management submodule is used to manage APIs by business group, and to achieve permission isolation and resource allocation.
7. A method for providing dynamic data services based on the system according to any one of claims 1 to 6, characterized in that, include: The web configuration center provides a visual interface to receive user configurations for data source connection parameters and API SQL templates, version numbers, and permission groups. When configuration changes occur, publish the configuration change event to the message middleware; Listen to the message middleware through the API query service, and dynamically update the data source connection pool and / or the pre-compiled SQL template corresponding to the API in local memory according to the configuration change event; The API query service receives a request from the caller, parses the parameters of the request, and matches the pre-compiled SQL template with the data source. The API query service executes pre-compiled SQL templates to query the corresponding data source and returns the query results to the requester.
8. The method according to claim 7, characterized in that Dynamically updating the pre-compiled SQL templates corresponding to the data source connection pool and / or API in local memory based on the configuration change event includes: When the change event is a new data source, initialize the data source connection pool and add the new data source to local memory; When the change event is a modification of the data source, the old data source connection pool is closed, and then the modified new data source is initialized and added to local memory; When the change event is a data source deletion, clear the local memory and connection pool corresponding to that data source. When the change event is a new API, the SQL template corresponding to the new API is pre-compiled, initialized, and cached in local memory; When the change event is an API modification, first delete the local cache of the API, precompile the SQL template corresponding to the modified API, initialize and cache it in local memory.
9. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method of claim 7 or 8.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method of claim 7 or 8.
11. A computer device, characterized in that, include: A memory on which computer programs are stored; A processor that, when executing the computer program, implements the steps of the method of claim 7 or 8; as well as A monitor is used to display a visual interface.