Data processing method, system, computer device, medium
By establishing a mapping relationship between storage requirement labels and storage characteristic labels in a low-code storage platform system, dynamically matching the target database, the problem that a single database design cannot meet the diverse data storage needs is solved, and efficient data processing and storage performance is achieved. Improve the scalability and intelligence of low-code development.
Patent Information
- Application Number
- CN202310363746.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-04-03
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2043-04-03
AI Technical Summary
When the existing low-code storage platform system faces data storage needs in diversified business fields, a single database design cannot meet complex storage requirements, resulting in a decrease in storage efficiency and affecting the scalability and performance of low-code development.
By establishing a mapping relationship between storage requirements labels and storage characteristic labels, dynamically determine the target database, implement data processing that matches application data and database characteristics, improve the flexibility and scalability of the storage framework, isolate data services and physical storage, and avoid Application development focuses on underlying storage selection.
It achieves the best fit between applications and databases, maximizes database performance, ensures storage performance in different business fields, and improves the scalability and intelligence of low-code storage platforms.
Smart Images

Figure CN118210510B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of database technology, and in particular to a data processing method, system, computer device and medium. Background Art
[0002] Low-code development is an emerging development model that can greatly improve application development efficiency and solve the problem of insufficient development capabilities in the application development field. Low-code data storage is one of the key subsystems of the low-code storage platform system, which is of great significance for supporting the development of efficient low-code applications on the low-code storage platform. As the low-code development model gradually matures and the business areas it supports continue to expand, data storage becomes more complex and changeable, and the requirements for the platform storage subsystem are also increasing. How to efficiently support the requirements of various business field applications for data storage and simplify application development is crucial to building a good low-code storage platform.
[0003] The field of low-code development support is developing rapidly, from simple light applications to complex industry applications, and from a single simple field to a variety of professional and complex business fields. Supporting application development in different business fields will also require the platform to meet the storage requirements of applications in various business fields. At the same time, the platform itself maintains good expansion capabilities to meet the requirements of potential business field applications. The original simple and single storage design is no longer sufficient to support the increasingly complex storage requirements. The current low-code industry lacks systematic consideration of this change. This deficiency will continue to magnify and will gradually become a constraint or even a bottleneck affecting the development of the low-code industry.
[0004] The current low-code storage platform system simply selects a single database to complete the storage of low-code metadata or application business data. For example, it selects the relational database vertical table method to record metadata, or uses a semi-structured database for storage. This method is simple to implement. For the early development of low-code, the characteristics of a database can be used to meet the business requirements of some low-code applications. However, as the low-code application field continues to develop, supporting various business fields has its own data processing requirements and storage requirements. A single database or simple storage design cannot meet the application scenarios of various data, and cannot guarantee the storage efficiency of the overall application support of the platform. Summary of the invention
[0005] The present disclosure provides a data processing method, system, computer device and medium.
[0006] In a first aspect, an embodiment of the present disclosure provides a data processing method, including:
[0007] Receive a first data processing request from an application, and obtain an application identifier carried in the first data processing request;
[0008] Determining a storage plug-in according to a storage characteristic label corresponding to the application identifier; wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label, the storage requirement label indicates a storage requirement of the application, and the storage characteristic label indicates a characteristic of a database used to store application data;
[0009] Determine a target database corresponding to the storage plug-in;
[0010] A data processing operation corresponding to the first data processing request is executed in the target database.
[0011] In yet another aspect, an embodiment of the present disclosure provides a data processing system, comprising a data service layer, a data adaptation layer, and a storage layer, wherein the storage layer comprises a database;
[0012] The data service layer is used to receive a first data processing request of an application, obtain an application identifier carried in the first data processing request, and determine a storage plug-in according to a storage characteristic label corresponding to the application identifier; wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label, the storage requirement label indicates a storage requirement of the application, and the storage characteristic label indicates a feature of a database used to store application data;
[0013] The data adaptation layer is used to determine a target database corresponding to the storage plug-in, and execute a data processing operation corresponding to the first data processing request in the target database.
[0014] On the other hand, an embodiment of the present disclosure further provides a computer device, comprising: one or more processors; a storage device on which one or more programs are stored; when the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method as described above.
[0015] On the other hand, an embodiment of the present disclosure further provides a computer-readable medium having a computer program stored thereon, wherein the program implements the data processing method as described above when executed.
[0016] The data processing method provided by the disclosed embodiment includes: receiving a first data processing request of an application, obtaining an application identifier carried in the first data processing request, and determining a storage plug-in according to a storage characteristic label corresponding to the application identifier, wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label; determining a target database corresponding to the storage plug-in, and executing a data processing operation corresponding to the first data processing request in the target database. The disclosed embodiment matches application data with the characteristics of the database itself by establishing a mapping relationship between a storage requirement label and a storage characteristic label. The mapping relationship can be flexibly defined, and the storage requirement label and the storage characteristic label are extensible, thereby improving the flexibility, extensibility and intelligence of the storage framework; isolating data services from actual physical storage, and realizing the decoupling of applications from physical storage, so that application development does not need to pay attention to the selection of underlying storage, and can achieve the best fit between the application and the database according to the storage requirements of the application, maximizing the best performance of the database, and ensuring the storage performance of the application in different business fields. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 A flowchart of a data processing method provided by an embodiment of the present disclosure;
[0018] Figure 2 A schematic diagram of a flow chart for performing data processing operations in a target database provided by an embodiment of the present disclosure;
[0019] Figure 3 A schematic diagram of a data processing flow provided for an embodiment of the present disclosure;
[0020] Figure 4 A schematic diagram of a process for creating an application provided in an embodiment of the present disclosure;
[0021] Figure 5 A schematic diagram of the structure of a data processing system provided in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0022] Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of the present disclosure.
[0023] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.
[0024] The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof is not excluded.
[0025] The embodiments described herein may be described with reference to plan views and / or cross-sectional views by means of idealized schematic diagrams of the present disclosure. Therefore, the example illustrations may be modified according to manufacturing techniques and / or tolerances. Therefore, the embodiments are not limited to the embodiments shown in the accompanying drawings, but include modifications of the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the accompanying drawings have schematic properties, and the shapes of the regions shown in the figures illustrate the specific shapes of the regions of the elements, but are not intended to be limiting.
[0026] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.
[0027] The present disclosure provides a data processing method, which is applied to a data processing system, such as Figure 5 As shown, the data processing system is used to store, modify, delete, read, and process application data (such as business data) of various applications. Applications may include but are not limited to strong transaction applications, hybrid applications, large-capacity applications, etc. In the embodiments of the present disclosure, the data processing system is taken as a low-code storage platform system for example. Figure 5 As shown, the low-code storage platform system includes a data service layer, a data adaptation layer and a storage layer. The storage layer includes a database. The data service layer is oriented to various applications and stores the access routes of each application to the database; the data adaptation layer is used to store the storage plug-ins of each database to achieve the matching of the application and the database, and to call the corresponding storage plug-in in each database to realize data processing; the database in the storage layer is a physical library for storing the application data of each application, including a relational database (RDMBS) or a non-relational database (NoSQL). Exemplarily, the database can be a MYSQL database, a Mongodb database, an Orcale database, an ElasticSearch database, etc.
[0028] Combination Figure 1 , Figure 3 and Figure 5 As shown, the data processing method comprises the following steps:
[0029] Step S11: receiving a first data processing request of an application, and obtaining an application identifier carried in the first data processing request.
[0030] The data service layer of the data processing system receives the first data processing request of each application, which includes but is not limited to requests for data storage, data query, data modification (data addition / data deletion), etc. The application identifier carried in the first data processing request is obtained by parsing the first data processing request to determine the application to be processed.
[0031] Step S12, determining the storage plug-in according to the storage characteristic label corresponding to the application identifier, wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and the storage characteristic label.
[0032] The storage requirement label indicates the storage requirement of the application. Different applications support different business areas and have their own data processing and storage requirements. Therefore, different applications correspond to different storage requirement labels. The storage feature label indicates the characteristics of the database used to store application data. Each database is configured with a storage feature label. The storage feature labels of different databases can be the same or different.
[0033] The data service layer stores the mapping relationship between the preset storage requirement label and the storage characteristic label and the storage characteristic label corresponding to each application. The storage characteristic label corresponding to each application reflects the routing information of data access, which is automatically generated and stored according to the mapping relationship between the storage requirement label and the storage characteristic label when each application is established. In this step, the storage characteristic label corresponding to the application identifier can be directly obtained from the data service layer, and the storage plug-in can be determined according to the obtained storage characteristic label.
[0034] Step S13, determining the target database corresponding to the storage plug-in.
[0035] The data processing system's data adaptation layer stores storage plug-ins for various databases. In this step, the data adaptation layer locates the target database based on the determined storage plug-in. This step can determine the storage strategy for application metadata and business data, and select one or more databases to complete data processing (e.g., store data). Application users do not need to pay direct attention to the storage solution of the application, but only need to describe the storage requirements of the application.
[0036] Step S14: executing a data processing operation corresponding to the first data processing request in the target database.
[0037] The data adaptation layer performs operations such as data storage, data query, data modification (data addition / data deletion) in the target database and returns the data processing results.
[0038] The data processing method provided by the disclosed embodiment includes: receiving a first data processing request of an application, obtaining an application identifier carried in the first data processing request, and determining a storage plug-in according to a storage characteristic label corresponding to the application identifier, wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label; determining a target database corresponding to the storage plug-in, and executing a data processing operation corresponding to the first data processing request in the target database. The disclosed embodiment matches application data with the characteristics of the database itself by establishing a mapping relationship between a storage requirement label and a storage characteristic label. The mapping relationship can be flexibly defined, and the storage requirement label and the storage characteristic label are extensible, thereby improving the flexibility, extensibility and intelligence of the storage framework; isolating data services from actual physical storage, and realizing the decoupling of applications from physical storage, so that application development does not need to pay attention to the selection of underlying storage, and can achieve the best fit between the application and the database according to the storage requirements of the application, maximizing the best performance of the database, and ensuring the storage performance of the application in different business fields.
[0039] In some embodiments, the language of the first data processing request is a preset database language, which includes but is not limited to a standard SQL language.
[0040] Accordingly, combined Figure 2 and Figure 3 As shown, the step of executing the data processing operation corresponding to the first data processing request in the target database (i.e., step S14) includes the following steps:
[0041] Step S141, converting a first data processing request in a preset database language into a second data processing request in a target database language.
[0042] In this step, the data adaptation layer performs database language conversion on the data processing request. For example, if the target database is a Mongodb database and the preset database is an SQL database, the standard SQL query statement is converted into a Mongodb query statement using Mongo syntax; if the target database is an ElasticSearch database and the preset database is an SQL database, the standard SQL query statement is converted into an ElasticSearch query statement using ES syntax.
[0043] Step S142: executing a data processing operation corresponding to the second data processing request in the target database.
[0044] In this step, operations such as data storage, data query, data modification (data addition / data deletion) corresponding to the second data processing request in the target database language are executed in the target database.
[0045] In some embodiments, the storage plug-in includes a storage instance, and each database implements various data processing operations through the storage instance of the storage plug-in.
[0046] The step of converting the first data processing request in the preset database language into the second data processing request in the target database language (i.e., step S141) includes the following steps: calling the storage instance of the storage plug-in, and using the storage instance to convert the first data processing request in the preset database language into the second data processing request in the target database language. That is, the data adaptation layer implements syntax conversion by calling the storage instance of the storage plug-in determined in step S12.
[0047] In some embodiments, Figure 5 As shown, an application includes at least one storage requirement label, that is, one or more storage requirement labels are configured for each application. At least one database corresponds to the same storage feature label and the same storage plug-in, that is, a storage feature label is configured for each database, and each database has a storage plug-in. Different databases may have the same or different storage feature labels, and their storage plug-ins may be the same or different.
[0048] In some embodiments, at least two different types of databases correspond to the same storage feature tag and the same storage plug-in. In the embodiments of the present disclosure, the types of databases include relational databases and non-relational databases, such as Figure 5 As shown in the figure, a relational database (RDBMS) and a non-relational database (NoSQL) can correspond to the same storage feature label and the same storage plug-in. In this case, the data of an application can be stored in the above two databases. Using a combination of multiple types of databases to jointly support the same storage feature makes the storage requirements of the application and the storage characteristics of the physical storage more adaptable and accurate, and can better cope with various possibilities of future development.
[0049] In some embodiments, before receiving the first data processing request of the application (ie, step S11), the data processing method may further include the following steps: creating an application, and determining a storage characteristic tag corresponding to the application identifier of each application.
[0050] like Figure 4 As shown, the creation of applications and determination of storage characteristic labels corresponding to application identifiers of each application include the following steps:
[0051] Step 21 : During the process of creating applications, a storage requirement tag is configured for each application.
[0052] When creating an application in the low-code storage platform system, select the storage requirements of the application and store the corresponding storage requirement tags in the schema (object collection) of the application to implement the configuration of the storage requirement tags.
[0053] Step 22: Determine the storage characteristic label corresponding to the application identifier of each application according to the storage requirement label and the preset mapping relationship.
[0054] The data service layer stores the mapping relationship between the storage requirement tag and the storage characteristic tag. In this step, during the application creation phase, the storage requirement tag of the application can be automatically queried based on the mapping relationship. Since the mapping relationship is stored with the application ID of the application as the index, the storage characteristic tag corresponding to each application can be stored in the data service layer with the application ID of the application as the index to record the routing information of data access, so that when the data of the application is subsequently processed, the corresponding database can be determined based on the routing information.
[0055] The present disclosure also provides a data processing system. Figure 5 As shown, the data processing system includes a data service layer, a data adaptation layer and a storage layer, and the storage layer includes a database.
[0056] The data service layer is used to receive a first data processing request of an application, obtain an application identifier carried in the first data processing request, and determine a storage plug-in according to a storage characteristic label corresponding to the application identifier; wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label, the storage requirement label indicates a storage requirement of the application, and the storage characteristic label indicates a characteristic of a database used to store application data;
[0057] The data adaptation layer is used to determine a target database corresponding to the storage plug-in, and execute a data processing operation corresponding to the first data processing request in the target database.
[0058] In some embodiments, the data processing system is a low-code storage platform system.
[0059] The following combination Figure 5 and Figure 3 , taking the low-code storage platform system as an example, the data storage architecture creation process and data processing process of the low-code storage platform system are explained in detail.
[0060] Step 1: Extract the data service layer, which provides DDL (Data Definition Language) and DML (Data Manipulation Language) operations to upper-layer applications, such as creating new database tables, adding new data, modifying data, deleting data, querying data, and paging data query. This layer isolates upper-layer applications from specific physical storage and unifies the external service capabilities of different physical storages.
[0061] According to the metadata definition application method, the northbound service interface and southbound adaptation interface of metadata for data storage are abstracted, and the business data and metadata are stored separately, while meeting the functional requirements, performance, capacity, security, multi-tenancy, permissions and management interface requirements of data plug-ins.
[0062] Manage application storage requirement tags and storage feature tags, and configure the mapping between the two.
[0063] Step 2: Define a unified input and output interface at the data service layer to normalize the parameters of the upper layer data request response.
[0064] Step 3, extract the data adaptation layer, unify the development protocol, do not need to pay attention to the protocol drivers of each database in the storage layer, establish and store the storage plug-in of each database to realize data storage.
[0065] Implement the southbound adapter interface to connect to different databases in the storage layer, complete the conversion from the service interface to the storage layer, shield the database differentiation, and define the storage feature labels of the database.
[0066] Deploy an actual combination of database and storage plugin instances to support southbound adapter interface requirements.
[0067] The above steps 1-3 are the low-code storage platform system creation process, and the following steps 4-5 are the low-code storage platform system data processing process.
[0068] Step 4: After receiving the DSL (Domain Specific Language) data processing request sent by the upper layer application through the query interface of the data service layer, the data service layer selects a storage plug-in according to the storage characteristic label (i.e., storage route) corresponding to the application identifier. The storage characteristic label is automatically determined when the application is created according to the mapping relationship between the preset storage requirement label and the storage characteristic label.
[0069] Step 5: The data adaptation layer determines the target database corresponding to the storage plug-in, calls the corresponding storage plug-in to perform database language conversion on the data processing request sent by the data service layer, converts it into the language of the target database, and performs corresponding data processing operations in the target database.
[0070] The disclosed embodiments are applied to a low-code storage platform system, supporting scenarios with differentiated demands for data storage in a variety of application development fields, as well as other scenarios with similar demands, such as data lake design scenarios.
[0071] The disclosed embodiments separate and convert data services and data physical storage, increase the flexibility and scalability of data storage, decouple application data from physical storage, and achieve optimal routing matching between application storage requirements and actual database storage capabilities through flexible configuration of application storage requirements and database storage characteristics.
[0072] The disclosed embodiment aims at the problem that a single database or a simple collaborative data storage architecture cannot meet the evolving data storage requirements in the low-code development application field, and provides a hierarchically designed data storage architecture, which separates application calls from physical storage, and introduces a mapping relationship between storage requirement labels and storage feature labels to achieve the best match between application and storage. By analyzing the support of the low-code storage platform system for application storage capabilities, the storage requirements of the low-code storage platform system and application data are abstracted to achieve the decoupling of storage requirements from databases. The characteristics of different databases are analyzed, storage feature labels are defined, different storage requirement labels are defined for the storage requirements of different types of applications, and the mapping relationship between storage requirement labels and storage feature labels is configured to form storage routes. Different storage plug-ins and their corresponding databases are automatically selected according to the storage routes to complete the storage call of application data, so as to achieve the best match between the application and the database's own characteristics, and fully exert the advantages of the database itself. The mapping relationship is flexible enough and customizable, and both storage feature labels and storage requirement labels are extensible, and the types of databases can be increased; multiple types of database combinations can be used to jointly support storage features, so that the storage requirements of applications and the storage features of databases are more adaptable and accurate, and can better cope with various possibilities of future development.
[0073] The disclosed embodiment uses the isolation of data services and physical storage to achieve the separation of low-code data services from the actual database. By associating the storage requirements of the application with the storage characteristics of the database, the scalability, flexibility and intelligence of the storage framework are increased. This makes it unnecessary for low-code application development to focus on the selection of underlying storage. The application and database can be optimally matched according to the storage requirements of the application, maximizing the best performance of the database and ensuring the storage performance of low-code applications in different business areas.
[0074] An embodiment of the present disclosure also provides a computer device, which includes: one or more processors and a storage device; wherein one or more programs are stored on the storage device, and when the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method provided in the aforementioned embodiments.
[0075] The embodiments of the present disclosure further provide a computer-readable medium on which a computer program is stored, wherein the computer program, when executed, implements the data processing method provided in the aforementioned embodiments.
[0076] It will be appreciated by those skilled in the art that all or some of the steps in the method disclosed above, the functional modules / units in the device may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.
[0077] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.
Claims
1. A data processing method, characterized in that: include: Receive a first data processing request from an application, and obtain an application identifier carried in the first data processing request; Determining a storage plug-in according to a storage characteristic label corresponding to the application identifier; wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label, the storage requirement label indicates a storage requirement of the application, the storage characteristic label indicates a feature of a database for storing application data, and reflects routing information for accessing database data; Determine a target database corresponding to the storage plug-in; A data processing operation corresponding to the first data processing request is executed in the target database.
2. The method according to claim 1, characterized in that The language of the first data processing request is a preset database language, and performing a data processing operation corresponding to the first data processing request in the target database includes: Converting a first data processing request in the preset database language into a second data processing request in the target database language; A data processing operation corresponding to the second data processing request is executed in the target database.
3. The method according to claim 2, characterized in that The storage plug-in includes a storage instance, and the converting the first data processing request in the preset database language into the second data processing request in the target database language includes: The storage instance of the storage plug-in is called, and the first data processing request in the preset database language is converted into a second data processing request in the target database language by using the storage instance.
4. The method according to claim 1, characterized in that Before receiving the first data processing request of the application, the method further includes: creating an application, and determining a storage characteristic tag corresponding to the application identifier of each of the applications; The step of creating an application and determining a storage characteristic tag corresponding to an application identifier of each application includes: In the process of creating the applications, configuring a storage requirement tag for each of the applications; The storage characteristic label corresponding to the application identifier of each of the applications is determined according to the storage requirement label and the preset mapping relationship.
5. The method according to claim 1, characterized in that An application includes at least one storage requirement tag, and at least one of the databases corresponds to the same storage characteristic tag and the same storage plug-in.
6. The method according to claim 5, characterized in that At least two different types of databases correspond to the same storage characteristic tag and the same storage plug-in.
7. The method according to any one of claims 1 to 6, characterized in that: The method is applied to a low-code storage platform system.
8. A data processing system, characterized in that: It includes a data service layer, a data adaptation layer and a storage layer, wherein the storage layer includes a database; The data service layer is used to receive a first data processing request of an application, obtain an application identifier carried in the first data processing request, and determine a storage plug-in according to a storage characteristic label corresponding to the application identifier; wherein the storage characteristic label is determined according to a mapping relationship between a preset storage requirement label and a storage characteristic label, the storage requirement label indicates a storage requirement of the application, the storage characteristic label indicates a feature of a database used to store application data, and reflects routing information for accessing database data; The data adaptation layer is used to determine a target database corresponding to the storage plug-in, and execute a data processing operation corresponding to the first data processing request in the target database.
9. A computer device, wherein: include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method according to any one of claims 1 to 7.
10. A computer readable medium having a computer program stored thereon, wherein: When the program is executed, the data processing method according to any one of claims 1 to 7 is implemented.
