Data processing method and device

Abstract

The present application provides a data processing method and device. The method extracts the functionality of docking between application services and data sources and encapsulates it in a docking module. Thus, during the application system development phase, a docking module only needs to be developed once, and the developed docking module has the functionality of docking with data sources, such as the functionality of docking with each data source separately. Deploying the developed docking module in the application system enables each application service in the application system to have the functionality of docking with each data source separately. This achieves the goal of developing "the functionality of docking with each data source separately" once and reusing it, avoiding the need to repeatedly develop the functionality of docking with data sources for different application services in the application system. This reduces development workload, reduces labor costs, and improves development efficiency.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method and device. Background Art

[0002] With the rapid development of technology, various application systems (such as enterprise management systems and service systems that provide data services to a large number of users) are emerging one after another. In order to improve the service capabilities of current application systems, current application systems often connect to a variety of different data sources, including databases, elasticsearch (search servers), and graph databases, so that the application system can interactively query data in a variety of different data sources when querying data for users, thereby improving the accuracy of the query. In addition, sometimes, according to actual needs, the application system needs to run on different cloud platforms in different situations. However, the data sources connected to different cloud platforms may be different. Therefore, in order for the application system to be able to query data for users when running on different cloud platforms, the application system also needs to connect to the data sources connected to different application platforms.

[0003] In order to enable the application system to connect to different data sources, in one approach, during the stage of developing the application system, it is necessary to deploy functions for connecting to different data sources in the application system.

[0004] In order to deploy the function of connecting to different data sources in the application system, it is necessary to write computer program codes for the function of connecting to different data sources in the application system.

[0005] The inventors discovered that sometimes, when an application system includes a single type of application service, computer program code for interfacing with different data sources needs to be written for that application service. Thus, during the application system development phase, the computer program code for interfacing with different data sources only needs to be written once within the application system.

[0006] However, sometimes an application system includes two or more different types of application services. For each application service, separate computer program code for interfacing with different data sources must be written. Thus, during the application system development phase, the computer program code for interfacing with different data sources must be written more than once. That is, if the application system includes several types of application services, the computer program code for interfacing with different data sources must be written several times.

[0007] As can be seen, the above situation results in a large development workload, high labor costs, and low development efficiency. Furthermore, if the application system subsequently needs to update the data source it interfaces with, computer program code for each application service in the application system must be written to update the data source, resulting in high labor costs and low update efficiency. Summary of the Invention

[0008] This application provides a data processing method and device.

[0009] In a first aspect, the present application provides a data processing method, which is applied to a computing device, wherein the computing device is loaded with an application system, the application system includes an application service, and the application system is connected to a data source; the application system also includes a docking module for docking with the data source; the method includes:

[0010] When the target application service in the application system submits a data processing request for a target data source among the data sources docked with the application system to the docking module, calling a data source management component created in advance in the docking module, calling a data source driver management component created in advance in the docking module, and calling an executor management component created in advance in the docking module;

[0011] The data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source; the data source driver management component is at least used to manage the driver of the data source connected to the application system; and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system;

[0012] Based on the data source management component, a target data source connection between the application system and the target data source is retrieved; based on the data source driver management component, a target driver of the target data source is retrieved; and based on the executor management component, a target executor corresponding to the target data source is retrieved;

[0013] Based on the target executor corresponding to the target data source and the target driver of the target data source connected via the target data source, the data processing request is processed in the target data source to obtain a processing result;

[0014] Return the processing result to the target application service.

[0015] In an optional implementation, the docking module is a docking module dedicated to the target application service, and the application system includes multiple docking modules for docking with data sources; each docking module is dedicated to a different application service in the application system, and different application services in the application system are respectively loaded with their own dedicated docking modules;

[0016] The data processing request is submitted by the target application service to the target application service-specific docking module loaded in the target application service.

[0017] In an optional implementation, the docking module is a docking module shared by application services in the application system;

[0018] The docking module is located in the middleware in the application system. The middleware is independent of each application service and has an application programming interface (API) open to the outside world.

[0019] The data processing request is submitted by the target application service to the docking module in the middleware based on the API.

[0020] In an optional implementation, the method further includes:

[0021] Upon receiving a deregistration operation submitted to the docking module for deregistering an old data source in the data source docked with the application system, calling a data source management component previously created in the docking module, calling a data source driver management component previously created in the docking module, and calling an executor management component previously created in the docking module;

[0022] In the data source management component, the data source connection between the application system and the old data source and the configuration information of the old data source are cancelled, in the data source driver management component, the driver of the old data source is cancelled, and in the executor management component, the executor corresponding to the old data source is cancelled.

[0023] In an optional implementation, the method further includes:

[0024] Upon receiving an add operation submitted to the docking module for adding a new data source for docking with the application system, obtaining a new driver for the new data source, obtaining new configuration information for the new data source, and obtaining a new executor corresponding to the new data source;

[0025] Retrieving a data source management component previously created in the docking module, retrieving a data source driver management component previously created in the docking module, and retrieving an executor management component previously created in the docking module;

[0026] A new data source connection is created between the application system and the new data source in the data source management component based on the new driver and the new configuration information, a new driver for the new data source is added in the data source driver management component, and a new executor corresponding to the new data source is added in the executor management component.

[0027] In an optional implementation, the method further includes:

[0028] Upon receiving a modification operation submitted to the docking module for modifying configuration information of an old data source in a data source docked with the application system, obtaining the modified configuration information of the old data source;

[0029] Retrieving a data source management component previously created in the docking module and a data source driver management component previously created in the docking module;

[0030] The old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component according to the old driver of the old data source in the data source driver management component and the modified configuration information of the old data source.

[0031] In an optional implementation, the method further includes:

[0032] Upon receiving a modification operation submitted to the docking module for modifying a driver of an old data source in a data source docked with the application system, obtaining the modified driver of the old data source;

[0033] Retrieving a data source management component previously created in the docking module and a data source driver management component previously created in the docking module;

[0034] An old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component according to the modified driver of the old data source and the old configuration information of the old data source in the data source management component, and the old driver of the old data source is replaced with the modified driver of the old data source in the data source driver management component.

[0035] In an optional implementation, the method further includes:

[0036] Upon receiving a modification operation submitted to the docking module for modifying an executor corresponding to an old data source in a data source docked with the application system, obtaining the modified executor corresponding to the old data source;

[0037] Retrieve the actuator management component previously created in the docking module;

[0038] In the executor management component, the modified executor corresponding to the old data source is used to replace the old executor corresponding to the old data source.

[0039] In a second aspect, the present application provides a data processing apparatus, which is applied to a computing device, wherein the computing device is loaded with an application system, the application system includes an application service, and the application system is connected to a data source; the application system also includes a docking module for docking with the data source; the apparatus includes:

[0040] a first calling module configured to call a data source management component pre-created in the docking module, a data source driver management component pre-created in the docking module, and an executor management component pre-created in the docking module when a target application service in the application system submits a data processing request for a target data source among the data sources docked with the application system to the docking module;

[0041] The data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source; the data source driver management component is at least used to manage the driver of the data source connected to the application system; and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system;

[0042] A second retrieval module is configured to retrieve a target data source connection between the application system and the target data source based on the data source management component; retrieve a target driver program of the target data source based on the data source driver management component; and retrieve a target executor corresponding to the target data source based on the executor management component;

[0043] A processing module, configured to process the data processing request in the target data source based on a target executor corresponding to the target data source and a target driver of the target data source connected via the target data source, and obtain a processing result;

[0044] The return module is used to return the processing result to the target application service.

[0045] In an optional implementation, the docking module is a docking module dedicated to the target application service, and the application system includes multiple docking modules for docking with data sources; each docking module is dedicated to a different application service in the application system, and different application services in the application system are respectively loaded with their own dedicated docking modules;

[0046] The data processing request is submitted by the target application service to the target application service-specific docking module loaded in the target application service.

[0047] In an optional implementation, the docking module is a docking module shared by application services in the application system;

[0048] The docking module is located in the middleware in the application system. The middleware is independent of each application service and has an application programming interface (API) open to the outside world.

[0049] The data processing request is submitted by the target application service to the docking module in the middleware based on the API.

[0050] In an optional implementation, the apparatus further includes:

[0051] a third retrieval module configured to, upon receiving a deregistration operation submitted to the docking module for deregistering an old data source in a data source docked with the application system, retrieve a data source management component previously created in the docking module, retrieve a data source driver management component previously created in the docking module, and retrieve an executor management component previously created in the docking module;

[0052] A deregistration module is used to deregister the data source connection between the application system and the old data source and the configuration information of the old data source in the data source management component, deregister the driver of the old data source in the data source driver management component, and deregister the executor corresponding to the old data source in the executor management component.

[0053] In an optional implementation, the apparatus further includes:

[0054] a first acquisition module configured to, upon receiving an add operation submitted to the docking module for adding a new data source for docking with the application system, acquire a new driver for the new data source, acquire new configuration information for the new data source, and acquire a new executor corresponding to the new data source;

[0055] a fourth calling module, configured to call a data source management component previously created in the docking module, call a data source driver management component previously created in the docking module, and call an executor management component previously created in the docking module;

[0056] An adding module is used to create a new data source connection between the application system and the new data source in the data source management component based on the new driver and the new configuration information, add a new driver for the new data source in the data source driver management component, and add a new executor corresponding to the new data source in the executor management component.

[0057] In an optional implementation, the apparatus further includes:

[0058] a second acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying configuration information of an old data source in a data source docked with the application system, acquire the modified configuration information of the old data source;

[0059] A fifth calling module, configured to call a data source management component created in advance in the docking module and a data source driver management component created in advance in the docking module;

[0060] The first creation module is used to cancel the old data source connection between the application system and the old data source in the data source management component, and to create a new data source connection between the application system and the old data source in the data source management component based on the old driver of the old data source in the data source driver management component and the modified configuration information of the old data source.

[0061] In an optional implementation, the apparatus further includes:

[0062] a third acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying a driver of an old data source in a data source docked with the application system, acquire the modified driver of the old data source;

[0063] a sixth calling module, configured to call a data source management component created in advance in the docking module and a data source driver management component created in advance in the docking module;

[0064] A second creation module is configured to cancel the old data source connection between the application system and the old data source in the data source management component, create a new data source connection between the application system and the old data source in the data source management component based on the modified driver of the old data source and the old configuration information of the old data source in the data source management component, and replace the old driver of the old data source with the modified driver of the old data source in the data source driver management component.

[0065] In an optional implementation, the apparatus further includes:

[0066] a fourth acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying an executor corresponding to an old data source in a data source docked with the application system, acquire the modified executor corresponding to the old data source;

[0067] A seventh calling module, used to call the actuator management component created in advance in the docking module;

[0068] A replacement module is used to replace the old executor corresponding to the old data source with the modified executor corresponding to the old data source in the executor management component.

[0069] In a third aspect, the present application provides a docking module, comprising:

[0070] Data source management component, data source driver management component, and executor management component;

[0071] The data source management component is at least used to manage the data source connection between the application system where the docking module is located and the data source docked by the application system and the configuration information of the docked data source, and to call the data source connection;

[0072] The data source driver management component is at least used to manage the driver of the data source docked with the application system where the docking module is located, and to call the driver of the docked data source;

[0073] The executor management component is at least used to manage the executor corresponding to the data source docked with the application system where the docking module is located, and to call the executor corresponding to the docked data source.

[0074] In a fourth aspect, the present application shows an electronic device, which includes: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the method shown in any of the aforementioned aspects.

[0075] In a fifth aspect, the present application shows a non-temporary computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the method shown in any of the aforementioned aspects.

[0076] In a sixth aspect, the present application shows a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to perform the method shown in any of the aforementioned aspects.

[0077] Compared with the prior art, this application has the following advantages:

[0078] In the present application, when a target application service in an application system submits a data processing request for a target data source in a data source docked with the application system to a docking module, the data source management component previously created in the docking module is called, the data source driver management component previously created in the docking module is called, and the executor management component previously created in the docking module is called; based on the data source management component, the target data source connection between the application system and the target data source is called. Based on the data source driver management component, the target driver of the target data source is called. And, based on the executor management component, the target executor corresponding to the target data source is called. Based on the target executor corresponding to the target data source and the target driver of the target data source, the data processing request is processed in the target data source via the target data source connection to obtain a processing result. The processing result is returned to the target application service.

[0079] Among them, the data source management component in the docking module of the present application is at least used to manage the data source connection between the application system and the data source docked with the application system and the configuration information of the data source, the data source driver management component is at least used to manage the driver program of the data source docked with the application system, and the executor management component is at least used to manage the executor corresponding to the data source docked with the application system.

[0080] In this way, the functionality of connecting application services with data sources is extracted and encapsulated in a connection module. Thus, during the application system development phase, a connection module only needs to be developed once, and the developed connection module has the functionality of connecting with data sources, for example, the functionality of connecting with each data source separately. By deploying the developed connection module in the application system, each application service in the application system can be enabled to connect with each data source separately. This eliminates the need to write computer program code for each application service in the application system to implement the functionality of connecting with each data source separately. This achieves the goal of developing the functionality of connecting with each data source separately once and reusing it, avoiding the need to repeatedly develop the functionality of connecting with data sources for different application services in the application system. This reduces development workload, labor costs, and improves development efficiency. Furthermore, the connection module does not intrude into the code in the application system, reducing the cost and difficulty of subsequent maintenance of the application system. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Figure 1 It is a flowchart of the steps of a data processing method of the present application.

[0082] Figure 2 This is a structural block diagram of a data processing device of the present application.

[0083] Figure 3 This is a structural block diagram of a device of the present application. DETAILED DESCRIPTION

[0084] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0085] The inventors have proposed the need to reduce labor costs and improve development efficiency and update efficiency.

[0086] In order to achieve the goal of reducing labor costs and improving development efficiency and update efficiency, the inventor conducted a statistical analysis of the causes of the defects in the above-mentioned situation and found that when the application system includes more than two different types of application services, the workload of developing the application system is very large. Therefore, the work of developing different application services in the application system is usually assigned to different development teams. These development teams are often independent of each other in their work, each has its own work criteria, and these development teams may not be in the same office location or the same city, etc., which leads to low communication efficiency or almost no communication between different developers. This results in that although the same application system is being developed, each development team often works independently when developing their respective application services.

[0087] As such, each development team needs to write computer program codes for functions of connecting to different data sources in their respective application services.

[0088] In one case, if the data sources that the application services assigned to each development team connect to are the same, then from the current situation, the computer program code for the functions of connecting to the same data source will be repeatedly written in the application services assigned to each development team, which will lead to duplicate development, resulting in a large development workload and a large update workload, high labor costs, low development efficiency and low update efficiency.

[0089] For this reason, in order to achieve the goal of reducing labor costs and improving development efficiency and update efficiency, the inventor thought of extracting the function of docking with the data source. For example, the computer program code for the function of docking with the data source is encapsulated into a module, which may include an SDK (Software Development Kit) and the like.

[0090] Specifically, see Figure 1 , shows a data processing method of the present application, which is applied to a computing device, which may include a cloud computing device or a local computing device, etc. The cloud computing device may include a computing device in a cloud platform, etc. The computing device is loaded with an application system, which includes application services (for example, one application service or multiple different application services), and the application system is connected to a data source (for example, one data source or multiple different data sources); the application system also includes a connection module for connecting to the data source; the method includes:

[0091] In step S101, when the target application service in the application system submits a data processing request for the target data source in the data source docked with the application system to the docking module, the data source management component created in advance in the docking module is called, the data source driver management component created in advance in the docking module is called, and the executor management component created in advance in the docking module is called.

[0092] Among them, the data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source, the data source driver management component is at least used to manage the driver program of the data source connected to the application system, and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system.

[0093] The configuration information of the data source may include the IP address (Internet Protocol Address) of the data source, the port number, and the account and password for the application system to log in to the data source.

[0094] In this application, in the scenario of developing an application system in advance, one or more different application services can be developed in the application system, and each application service needs to be connected to at least one data source. In one possible case, each application service needs to be connected to two or more different data sources.

[0095] For any application service in the application system, if the application service needs to connect to a data source, the developed connection module can be deployed in the application service. The same is true for every other application service in the application system.

[0096] Alternatively, the docking module may be deployed in a location in the application system that is independent of each application service, and each application service may share the docking module.

[0097] The docking module includes at least a data source management component, a data source driver management component, and an executor management component. In one example, the data source management component is used to manage at least the data source connections between the application system and each of multiple different data sources, as well as the configuration information of each data source. The data source driver management component is used to manage at least the drivers for each of the multiple different data sources. The executor management component is used to manage at least the executors corresponding to each of the multiple different data sources.

[0098] In an example, the data source management component may include but is not limited to: database data source management functions implemented based on MySQL and DRU ID, supporting access to databases such as MySQL, PostgreSQL, GaussDB, Kingbase, and Oceanbase; ELASTIC Search data source management functions implemented based on the ELASTIC Search docking module; and Neo4j / Nebu La graph database data source management functions implemented based on the Neo4j / Nebu La docking module, etc.

[0099] The data source driver management component can provide the data source management component with the ability to load and unload the data source driver. During the operation of the application system, the corresponding data source driver startup program can be loaded on demand in the data source driver management component.

[0100] Data source driver management components include but are not limited to: JDBC drivers for databases such as MySQL, PostgreSQL, GaussDB, and PostgreSQL; docking modules for Elastic Search; and docking modules for graph libraries such as Neo4j and Nebula.

[0101] The executor management component selects the corresponding type of executor based on the data processing request input by the user and the identification information of the target data source, obtains a valid data source connection from the data source management component, and sends the data processing request to the target data source.

[0102] Executor management components include but are not limited to: SQL executor for executing database queries, DSL executor for executing elastic search queries, and GQL executor for users to execute graph database queries.

[0103] When a target application service among multiple different application services submits a data processing request to the docking module for the target data source docked with the application system (if the application system docks with one data source, the target data source is this one data source, or if the application system docks with two or more data sources, the target data source is one of the two or more data sources), if the target data source is the data source docked with the application system, the target data source connection between the application system and the target data source can be retrieved based on the data source management component. The target driver of the target data source can be retrieved based on the data source driver management component. And, the target executor corresponding to the target data source can be retrieved based on the executor management component.

[0104] Alternatively, if the target data source is not the data source for docking with the application system, the target driver of the target data source, the target configuration information of the target data source, and the target executor corresponding to the target data source are obtained from the database corresponding to the docking module; the target driver of the target data source, the target configuration information of the target data source, and the target executor corresponding to the target data source can be developed in advance by the developer and stored in the database corresponding to the docking module, so that the subsequent docking module can call from the database when needed.

[0105] The data source management component, data source driver management component, and executor management component previously created in the docking module are then called. Based on the new driver and configuration information, a new data source connection is created between the application system and the new data source in the data source management component. A new driver for the new data source is added to the data source driver management component. Furthermore, a new executor corresponding to the new data source is added to the executor management component. Step S102 is then executed.

[0106] In step S102, the target data source connection between the application system and the target data source is retrieved based on the data source management component. The target driver of the target data source is retrieved based on the data source driver management component. And, the target executor corresponding to the target data source is retrieved based on the executor management component.

[0107] The data source management component can manage a connection pool between the application system and the target data source. The connection pool includes at least one target data source connection between the application system and the target data source. An available target data source connection can be selected from the at least one target data source connection.

[0108] Among them, in addition to managing the connection pool between the application system and the target data source, the data source management component may also manage the connection pool between the application system and other data sources. In this way, the connection pool between the application system and the target data source can be indexed from the data source management component according to the identification information of the target data source.

[0109] Among them, in addition to managing the target driver of the target data source, the data source management driver component may also manage target drivers of other data sources. In this way, the target driver of the target data source can be indexed from the data source driver management component according to the identification information of the target data source.

[0110] Among them, in addition to managing the target executor corresponding to the target data source, the executor management component may also manage executors corresponding to other data sources. In this way, the target executor corresponding to the target data source can be indexed from the executor management component according to the identification information of the target data source.

[0111] In step S103, based on the target executor corresponding to the target data source and the target driver of the target data source, the data processing request is processed in the target data source via the target data source connection to obtain a processing result.

[0112] By connecting to the target data source, interaction with the target data source can be achieved. If data processing requests need to be processed in the target data source, the target executor corresponding to the target data source and the target driver of the target data source need to be used. The target executor corresponding to the target data source has an interaction method for the underlying interaction with the data in the target data source, etc. The target driver of the target data source may include a calculation method for calculating the data in the target data source (for example, including some calculation functions for the target executor corresponding to the target data source to call, etc.).

[0113] In this way, it is necessary to connect to the target data source based on the target executor corresponding to the target data source and the target driver of the target data source, process the data processing request in the target data source, and obtain the processing result.

[0114] In step S104, the processing result is returned to the target application service.

[0115] In the present application, when a target application service in an application system submits a data processing request for a target data source in a data source docked with the application system to a docking module, the data source management component previously created in the docking module is called, the data source driver management component previously created in the docking module is called, and the executor management component previously created in the docking module is called; based on the data source management component, the target data source connection between the application system and the target data source is called. Based on the data source driver management component, the target driver of the target data source is called. And, based on the executor management component, the target executor corresponding to the target data source is called. Based on the target executor corresponding to the target data source and the target driver of the target data source, the data processing request is processed in the target data source via the target data source connection to obtain a processing result. The processing result is returned to the target application service.

[0116] Among them, the data source management component in the docking module of the present application is at least used to manage the data source connection between the application system and the data source docked with the application system and the configuration information of the data source, the data source driver management component is at least used to manage the driver program of the data source docked with the application system, and the executor management component is at least used to manage the executor corresponding to the data source docked with the application system.

[0117] In this way, the functionality for interfacing between application services and data sources is extracted and encapsulated in an interfacing module. Thus, during the application system development phase, a single interfacing module only needs to be developed, and the developed interfacing module has the functionality for interfacing with data sources, such as the functionality for interfacing with various data sources. Deploying the developed interfacing module in the application system enables each application service in the application system to have the functionality for interfacing with various data sources. This eliminates the need to write computer program code for each application service in the application system to implement the functionality for interfacing with various data sources. This achieves the goal of developing the functionality for interfacing with various data sources once and reusing it, avoiding the need to repeatedly develop the functionality for interfacing with data sources for different application services in the application system. This reduces development workload, labor costs, and improves development efficiency. Furthermore, the interfacing module does not intrude into the code in the application system, reducing the cost and difficulty of subsequent maintenance of the application system.

[0118] In one embodiment of the present application, the docking module is a docking module exclusive to the target application service, and the application system includes multiple docking modules for docking with data sources; each docking module is exclusive to a different application service in the application system, and multiple different application services in the application system are respectively loaded with their own exclusive docking modules; the data processing request is submitted by the target application service to the docking module exclusive to the target application service loaded in the target application service.

[0119] Alternatively, in another embodiment of the present application, the docking module is a docking module shared by multiple different application services included in the application system; the docking module is located in the middleware in the application system, the middleware is independent of each application service, and the middleware has an application programming interface API (such as Restful API, etc.) open to the outside world; the data processing request is submitted by the target application service to the docking module in the middleware based on the API.

[0120] In one embodiment of the present application, dynamic updating of the data source docked with the application system is supported in the docking module in the application system. For example, if the application system no longer needs to dock with the old data source, the relevant information of the old data source can be dynamically deregistered in the docking module in the application system.

[0121] For example, a deregistration operation for deregistering an old data source in the data source connected to the application system may be submitted to the connection module.

[0122] In this way, when the electronic device receives a deregistration operation submitted to the docking module to deregister the old data source from the data source docked with the application system, it can call the data source management component previously created in the docking module, call the data source driver management component previously created in the docking module, and call the executor management component previously created in the docking module. The data source management component then deregisters the data source connection between the application system and the old data source, as well as the old data source configuration information. The data source driver management component deregisters the old data source driver. Finally, the executor management component deregisters the executor corresponding to the old data source.

[0123] The docking module described in this embodiment can include a docking module shared by multiple application services in the application system, or a docking module loaded separately by each application service in the application system. This allows all docking modules in the application system to be updated with a single deregistration operation, reducing subsequent update costs and improving subsequent update efficiency. Old data sources can be deregistered from the application system without writing code in the application system.

[0124] In one embodiment of the present application, dynamic updating of the data source docked with the application system is supported in the docking module in the application system. For example, if the application system needs to dock with a new data source, relevant information of the new data source can be dynamically added to the docking module in the application system.

[0125] For example, an addition operation for adding a new data source for docking with the application system may be submitted to the docking module.

[0126] In this way, when the electronic device receives an addition operation submitted to the docking module for adding a new data source for docking with the application system, it obtains a new driver for the new data source, obtains new configuration information for the new data source, and obtains a new executor corresponding to the new data source.

[0127] The new driver program for the new data source, the new configuration information for the new data source, and the new actuator corresponding to the new data source may all be manually input. Thus, the electronic device may obtain the manually input new driver program for the new data source, the new configuration information for the new data source, and the new actuator corresponding to the new data source.

[0128] The data source management component, data source driver management component, and executor management component, all previously created in the docking module, are then called. Based on the new driver and configuration information, a new data source connection is created between the application system and the new data source in the data source management component. A new driver for the new data source is added to the data source driver management component, and a new executor corresponding to the new data source is added to the executor management component.

[0129] In this way, the data source management component can then be used to call a new data source connection between the application system and the new data source. The data source driver management component can be used to call a new driver for the new data source. Furthermore, the executor management component can be used to call a new executor corresponding to the new data source. Using the new executor and the new driver, the application can interact with the new data source via the new data source connection, for example, querying data in the new data source.

[0130] The docking module described in this embodiment can include a single docking module shared by multiple application services within the application system, or a docking module loaded separately by each application service within the application system. This allows a single add operation to update all docking modules within the application system, reducing subsequent update costs and improving subsequent update efficiency. This eliminates the need to write code within the application system to expand new data sources.

[0131] In one embodiment of the present application, dynamic updating of the data source docked with the application system is supported in the docking module in the application system. For example, if the application system needs to change the old data source that has been docked, the relevant information of the old data source can be dynamically modified in the docking module in the application system.

[0132] For example, in one example, when a modification operation submitted to the docking module is received for modifying the configuration information of the old data source in the data source docked with the application system, the modified configuration information of the old data source is obtained; the data source management component created in advance in the docking module and the data source driver management component created in advance in the docking module are called; the old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component based on the old driver of the old data source in the data source driver management component and the modified configuration information of the old data source.

[0133] In another example, upon receiving a modification operation submitted to a docking module for modifying a driver of an old data source in a data source docked with an application system, the modified driver of the old data source is obtained; a data source management component previously created in the docking module and a data source driver management component previously created in the docking module are called; the old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component based on the modified driver of the old data source and the old configuration information of the old data source in the data source management component, and the old driver of the old data source is replaced with the modified driver of the old data source in the data source driver management component.

[0134] In another example, when a modification operation is received, which is submitted to the docking module and is used to modify the executor corresponding to the old data source in the data source docked with the application system, the modified executor corresponding to the old data source is obtained; the executor management component created in advance in the docking module is called; and the old executor corresponding to the old data source is used in the executor management component to replace the old executor corresponding to the old data source.

[0135] The docking module described in this embodiment can include a single docking module shared by multiple application services within the application system, or a docking module loaded separately by each application service within the application system. This allows a single modification operation to update all docking modules within the application system, reducing subsequent update costs and improving subsequent update efficiency. This eliminates the need to write code within the application system to modify old data sources.

[0136] It should be noted that for the method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions involved are not necessarily required by this application.

[0137] Reference Figure 2 , shows a structural block diagram of a data processing device of the present application, which is applied to a computing device, wherein the computing device is loaded with an application system, the application system includes application services, and the application system is connected to a data source; the application system also includes a docking module for docking with the data source; the device includes:

[0138] A first calling module 11 is configured to call a data source management component created in advance in the docking module, call a data source driver management component created in advance in the docking module, and call an executor management component created in advance in the docking module when a target application service in the application system submits a data processing request for a target data source among the data sources docked with the application system to the docking module;

[0139] The data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source; the data source driver management component is at least used to manage the driver of the data source connected to the application system; and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system;

[0140] A second retrieval module 12 is configured to retrieve a target data source connection between the application system and the target data source based on the data source management component; retrieve a target driver of the target data source based on the data source driver management component; and retrieve a target executor corresponding to the target data source based on the executor management component;

[0141] A processing module 13 is configured to process the data processing request in the target data source based on a target executor corresponding to the target data source and a target driver of the target data source connected via the target data source to obtain a processing result;

[0142] The return module is used to return the processing result to the target application service.

[0143] In an optional implementation, the docking module is a docking module dedicated to the target application service, and the application system includes multiple docking modules for docking with data sources; each docking module is dedicated to a different application service in the application system, and different application services in the application system are respectively loaded with their own dedicated docking modules;

[0144] The data processing request is submitted by the target application service to the target application service-specific docking module loaded in the target application service.

[0145] In an optional implementation, the docking module is a docking module shared by application services in the application system;

[0146] The docking module is located in the middleware in the application system. The middleware is independent of each application service and has an application programming interface (API) open to the outside world.

[0147] The data processing request is submitted by the target application service to the docking module in the middleware based on the API.

[0148] In an optional implementation, the apparatus further includes:

[0149] a third retrieval module configured to, upon receiving a deregistration operation submitted to the docking module for deregistering an old data source in a data source docked with the application system, retrieve a data source management component previously created in the docking module, retrieve a data source driver management component previously created in the docking module, and retrieve an executor management component previously created in the docking module;

[0150] A deregistration module is used to deregister the data source connection between the application system and the old data source and the configuration information of the old data source in the data source management component, deregister the driver of the old data source in the data source driver management component, and deregister the executor corresponding to the old data source in the executor management component.

[0151] In an optional implementation, the apparatus further includes:

[0152] a first acquisition module configured to, upon receiving an add operation submitted to the docking module for adding a new data source for docking with the application system, acquire a new driver for the new data source, acquire new configuration information for the new data source, and acquire a new executor corresponding to the new data source;

[0153] a fourth calling module, configured to call a data source management component previously created in the docking module, call a data source driver management component previously created in the docking module, and call an executor management component previously created in the docking module;

[0154] An adding module is used to create a new data source connection between the application system and the new data source in the data source management component based on the new driver and the new configuration information, add a new driver for the new data source in the data source driver management component, and add a new executor corresponding to the new data source in the executor management component.

[0155] In an optional implementation, the apparatus further includes:

[0156] a second acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying configuration information of an old data source in a data source docked with the application system, acquire the modified configuration information of the old data source;

[0157] A fifth calling module, configured to call a data source management component created in advance in the docking module and a data source driver management component created in advance in the docking module;

[0158] The first creation module is used to cancel the old data source connection between the application system and the old data source in the data source management component, and to create a new data source connection between the application system and the old data source in the data source management component based on the old driver of the old data source in the data source driver management component and the modified configuration information of the old data source.

[0159] In an optional implementation, the apparatus further includes:

[0160] a third acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying a driver of an old data source in a data source docked with the application system, acquire the modified driver of the old data source;

[0161] a sixth calling module, configured to call a data source management component created in advance in the docking module and a data source driver management component created in advance in the docking module;

[0162] A second creation module is configured to cancel the old data source connection between the application system and the old data source in the data source management component, create a new data source connection between the application system and the old data source in the data source management component based on the modified driver of the old data source and the old configuration information of the old data source in the data source management component, and replace the old driver of the old data source with the modified driver of the old data source in the data source driver management component.

[0163] In an optional implementation, the apparatus further includes:

[0164] a fourth acquisition module configured to, upon receiving a modification operation submitted to the docking module for modifying an executor corresponding to an old data source in a data source docked with the application system, acquire the modified executor corresponding to the old data source;

[0165] A seventh calling module, used to call the actuator management component created in advance in the docking module;

[0166] A replacement module is used to replace the old executor corresponding to the old data source with the modified executor corresponding to the old data source in the executor management component.

[0167] In the present application, when a target application service in an application system submits a data processing request for a target data source in a data source docked with the application system to a docking module, the data source management component previously created in the docking module is called, the data source driver management component previously created in the docking module is called, and the executor management component previously created in the docking module is called; based on the data source management component, the target data source connection between the application system and the target data source is called. Based on the data source driver management component, the target driver of the target data source is called. And, based on the executor management component, the target executor corresponding to the target data source is called. Based on the target executor corresponding to the target data source and the target driver of the target data source, the data processing request is processed in the target data source via the target data source connection to obtain a processing result. The processing result is returned to the target application service.

[0168] Among them, the data source management component in the docking module of the present application is at least used to manage the data source connection between the application system and the data source docked with the application system and the configuration information of the data source, the data source driver management component is at least used to manage the driver program of the data source docked with the application system, and the executor management component is at least used to manage the executor corresponding to the data source docked with the application system.

[0169] In this way, the functionality for interfacing between application services and data sources is extracted and encapsulated in an interfacing module. Thus, during the application system development phase, a single interfacing module only needs to be developed, and the developed interfacing module has the functionality for interfacing with data sources, such as the functionality for interfacing with various data sources. Deploying the developed interfacing module in the application system enables each application service in the application system to have the functionality for interfacing with various data sources. This eliminates the need to write computer program code for each application service in the application system to implement the functionality for interfacing with various data sources. This achieves the goal of developing the functionality for interfacing with various data sources once and reusing it, avoiding the need to repeatedly develop the functionality for interfacing with data sources for different application services in the application system. This reduces development workload, labor costs, and improves development efficiency. Furthermore, the interfacing module does not intrude into the code in the application system, reducing the cost and difficulty of subsequent maintenance of the application system.

[0170] In addition, the present application also shows a docking module, which includes: a data source management component, a data source driver management component and an executor management component. The data source management component is at least used to manage the data source connection between the application system where the docking module is located and the data source docked by the application system and the configuration information of the docked data source, and is used to call the data source connection. The data source driver management component is at least used to manage the driver program of the data source docked by the application system where the docking module is located, and is used to call the driver program of the docked data source. The executor management component is at least used to manage the executor corresponding to the data source docked by the application system where the docking module is located, and is used to call the executor corresponding to the docked data source.

[0171] An embodiment of the present application further provides a non-volatile readable storage medium, which stores one or more modules (programs). When the one or more modules are applied to a device, the device can execute instructions (instructions) of each method step in the embodiment of the present application.

[0172] The present application provides one or more machine-readable media having instructions stored thereon, which, when executed by one or more processors, cause an electronic device to perform one or more of the methods described in the above embodiments. In the present application, the electronic device includes a server, a gateway, a sub-device, and the like, wherein the sub-device is an IoT device or other device.

[0173] The embodiments of the present disclosure may be implemented as an apparatus configured as desired using any appropriate hardware, firmware, software, or any combination thereof, which may include a server (cluster), terminal devices such as IoT devices, and other electronic devices.

[0174] Figure 3 An exemplary apparatus 1300 that can be used to implement various embodiments of the present application is schematically shown.

[0175] For one embodiment, Figure 3 An exemplary apparatus 1300 is shown having one or more processors 1302, a control module (chip set) 1304 coupled to at least one of the processor(s) 1302, a memory 1306 coupled to the control module 1304, a non-volatile memory (NVM) / storage device 1308 coupled to the control module 1304, one or more input / output devices 1310 coupled to the control module 1304, and a network interface 1312 coupled to the control module 1304.

[0176] The processor 1302 may include one or more single-core or multi-core processors, and the processor 1302 may include any combination of general-purpose processors or dedicated processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 1300 can serve as a server device such as a gateway in the embodiments of the present application.

[0177] In some embodiments, the apparatus 1300 may include one or more computer-readable media (e.g., memory 1306 or NVM / storage 1308) having instructions 1314 and one or more processors 1302 configured in conjunction with the one or more computer-readable media to execute the instructions 1314 to implement a module to perform the actions of the present disclosure.

[0178] For one embodiment, the control module 1304 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 1302 and / or any suitable device or component in communication with the control module 1304 .

[0179] The control module 1304 may include a memory controller module to provide an interface to the memory 1306. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0180] The memory 1306 can be used, for example, to load and store data and / or instructions 1314 for the device 1300. For one embodiment, the memory 1306 can include any suitable volatile memory, such as a suitable DRAM. In some embodiments, the memory 1306 can include double data rate quad synchronous dynamic random access memory (DDR4 SDRAM).

[0181] For one embodiment, control module 1304 may include one or more input / output controllers to provide interfaces to NVM / storage device 1308 and input / output device(s) 1310 .

[0182] For example, NVM / storage 1308 may be used to store data and / or instructions 1314. NVM / storage 1308 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives (HDDs), one or more compact disk (CD) drives, and / or one or more digital versatile disk (DVD) drives).

[0183] NVM / storage device 1308 may include storage resources that are physically part of the device on which apparatus 1300 is installed, or it may be accessible to the device without being part of the device. For example, NVM / storage device 1308 may be accessible over a network via input / output device(s) 1310.

[0184] (One or more) input / output devices 1310 may provide an interface for apparatus 1300 to communicate with any other appropriate device. Input / output devices 1310 may include a communication component, a phonetic component, a sensor component, etc. Network interface 1312 may provide an interface for apparatus 1300 to communicate via one or more networks. Apparatus 1300 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, for example, accessing a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof for wireless communication.

[0185] For one embodiment, at least one of the processor(s) 1302 may be packaged together with the logic of one or more controllers of the control module 1304 (e.g., a memory controller module). For one embodiment, at least one of the processor(s) 1302 may be packaged together with the logic of one or more controllers of the control module 1304 to form a system-in-package (SiP). For one embodiment, at least one of the processor(s) 1302 may be integrated on the same die with the logic of one or more controllers of the control module 1304. For one embodiment, at least one of the processor(s) 1302 may be integrated on the same die with the logic of one or more controllers of the control module 1304 to form a system-on-chip (SoC).

[0186] In various embodiments, the apparatus 1300 may be, but is not limited to, a terminal device such as a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, the apparatus 1300 may have more or fewer components and / or a different architecture. For example, in some embodiments, the apparatus 1300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0187] An embodiment of the present application provides an electronic device, comprising: one or more processors; and one or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, enable the electronic device to perform one or more methods as described in the present application.

[0188] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0189] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0190] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, and the combination of the processes and / or boxes in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable information processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable information processing terminal device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0191] These computer program instructions may also be stored in a computer readable memory that can guide a computer or other programmable information processing terminal device to work in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0192] These computer program instructions can also be loaded onto a computer or other programmable information processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable terminal device. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0193] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0194] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0195] The data processing method and device provided by the present application are introduced in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. At the same time, for those skilled in the art, according to the idea of ​​the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present application.

Claims

1. A data processing method, characterized in that: Applied to a computing device, wherein the computing device is loaded with an application system, the application system includes application services, and the application system is connected to a data source; the application system also includes a docking module for docking with the data source; the method includes: When the target application service in the application system submits a data processing request for a target data source among the data sources docked with the application system to the docking module, calling a data source management component created in advance in the docking module, calling a data source driver management component created in advance in the docking module, and calling an executor management component created in advance in the docking module; The data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source; the data source driver management component is at least used to manage the driver of the data source connected to the application system; and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system; Based on the data source management component, a target data source connection between the application system and the target data source is retrieved; based on the data source driver management component, a target driver of the target data source is retrieved; and based on the executor management component, a target executor corresponding to the target data source is retrieved; Based on the target executor corresponding to the target data source and the target driver of the target data source connected via the target data source, the data processing request is processed in the target data source to obtain a processing result; Return the processing result to the target application service.

2. The method according to claim 1, characterized in that The docking module is a docking module dedicated to the target application service. The application system includes multiple docking modules for docking with data sources. Each docking module is dedicated to a different application service in the application system, and different application services in the application system are respectively loaded with their own dedicated docking modules. The data processing request is submitted by the target application service to the target application service-specific docking module loaded in the target application service.

3. The method according to claim 1, characterized in that The docking module is a docking module shared by application services in the application system; The docking module is located in the middleware in the application system. The middleware is independent of each application service and has an application programming interface (API) open to the outside world. The data processing request is submitted by the target application service to the docking module in the middleware based on the API.

4. The method according to claim 1, wherein The method further comprises: Upon receiving a deregistration operation submitted to the docking module for deregistering an old data source in the data source docked with the application system, calling a data source management component previously created in the docking module, calling a data source driver management component previously created in the docking module, and calling an executor management component previously created in the docking module; In the data source management component, the data source connection between the application system and the old data source and the configuration information of the old data source are cancelled, in the data source driver management component, the driver of the old data source is cancelled, and in the executor management component, the executor corresponding to the old data source is cancelled.

5. The method according to claim 1, wherein The method further comprises: Upon receiving an add operation submitted to the docking module for adding a new data source for docking with the application system, obtaining a new driver for the new data source, obtaining new configuration information for the new data source, and obtaining a new executor corresponding to the new data source; Retrieving a data source management component previously created in the docking module, retrieving a data source driver management component previously created in the docking module, and retrieving an executor management component previously created in the docking module; A new data source connection is created between the application system and the new data source in the data source management component based on the new driver and the new configuration information, a new driver for the new data source is added in the data source driver management component, and a new executor corresponding to the new data source is added in the executor management component.

6. The method according to claim 1, characterized in that The method further comprises: Upon receiving a modification operation submitted to the docking module for modifying configuration information of an old data source in a data source docked with the application system, obtaining the modified configuration information of the old data source; Retrieving a data source management component previously created in the docking module and a data source driver management component previously created in the docking module; The old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component according to the old driver of the old data source in the data source driver management component and the modified configuration information of the old data source.

7. The method according to claim 1, characterized in that The method further comprises: Upon receiving a modification operation submitted to the docking module for modifying a driver of an old data source in a data source docked with the application system, obtaining the modified driver of the old data source; Retrieving a data source management component previously created in the docking module and a data source driver management component previously created in the docking module; An old data source connection between the application system and the old data source is cancelled in the data source management component, and a new data source connection between the application system and the old data source is created in the data source management component according to the modified driver of the old data source and the old configuration information of the old data source in the data source management component, and the old driver of the old data source is replaced with the modified driver of the old data source in the data source driver management component.

8. The method according to claim 1, characterized in that The method further comprises: Upon receiving a modification operation submitted to the docking module for modifying an executor corresponding to an old data source in a data source docked with the application system, obtaining the modified executor corresponding to the old data source; Retrieve the actuator management component previously created in the docking module; In the executor management component, the modified executor corresponding to the old data source is used to replace the old executor corresponding to the old data source.

9. A data processing device, characterized in that: Applied to a computing device, wherein the computing device is loaded with an application system, the application system includes application services, and the application system is connected to a data source; the application system also includes a docking module for docking with the data source; the device includes: a first calling module configured to call a data source management component pre-created in the docking module, a data source driver management component pre-created in the docking module, and an executor management component pre-created in the docking module when a target application service in the application system submits a data processing request for a target data source among the data sources docked with the application system to the docking module; The data source management component is at least used to manage the data source connection between the application system and the data source connected to the application system and the configuration information of the data source; the data source driver management component is at least used to manage the driver of the data source connected to the application system; and the executor management component is at least used to manage the executor corresponding to the data source connected to the application system; A second retrieval module is configured to retrieve a target data source connection between the application system and the target data source based on the data source management component; retrieve a target driver program of the target data source based on the data source driver management component; and retrieve a target executor corresponding to the target data source based on the executor management component; A processing module, configured to process the data processing request in the target data source based on a target executor corresponding to the target data source and a target driver of the target data source connected via the target data source, and obtain a processing result; The return module is used to return the processing result to the target application service.

10. A docking module, characterized in that: The docking module includes: Data source management component, data source driver management component, and executor management component; The data source management component is at least used to manage the data source connection between the application system where the docking module is located and the data source docked by the application system and the configuration information of the docked data source, and to call the data source connection; The data source driver management component is at least used to manage the driver of the data source docked with the application system where the docking module is located, and to call the driver of the docked data source; the data source driver management component provides the data source management component with the ability to load and unload the driver of the docked data source; The executor management component is at least used to manage the executor corresponding to the data source docked with the application system where the docking module is located, and to call the executor corresponding to the docked data source.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the method according to any one of claims 1 to 8 are implemented.

12. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images