Data storage method and device, electronic equipment and computer readable storage medium

Abstract

The data storage method and device, the electronic equipment and the computer readable storage medium provided by the present disclosure can be applied to the field of big data technology and can also be used in the field of financial technology. The data storage method comprises the following steps: in response to a data call request, first target business data to be stored is obtained from a first business system by calling a first data interface associated with the first business system; a target relationship mapping table established for a target service is read from at least one relationship mapping table in a corrosion-resistant layer, and a target general table established for the target service is read from at least one general table in the corrosion-resistant layer; and the first target business data is converted into target general data based on first storage relationship configuration information extracted from the target relationship mapping table, and the target general data is newly stored in the target general table.

Description

Technical Field

[0001] This disclosure relates to the field of big data technology, and more specifically to a data storage method, apparatus, device, medium, and program product. Background Technology

[0002] With the continuous improvement of information services, data interaction between various business systems is becoming increasingly frequent. A complete closed loop of a business process requires querying and analyzing a large amount of relevant data to arrive at the correct conclusions. Storing relevant data not only facilitates rapid retrieval and use in business operations, but is also a crucial foundation for discovering related problems and generating data reports.

[0003] In realizing the concept disclosed herein, the inventors discovered at least the following problems in the related technologies: Current data storage solutions are usually designed for specific scenarios. Data callers distinguish between data storage from a business dimension (storing to the business master table) or a service dimension (each service has at least one data table). This is limited to specific scenarios, and every change in data means a modification to the storage structure, increasing the complexity of data storage and use for the caller. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a method, apparatus, device, medium and program product for data storage.

[0005] One aspect of this disclosure provides a data storage method, comprising:

[0006] In response to a data call request, the system retrieves the first target business data to be stored from the first business system by calling the first data interface associated with the first business system. The first target business data originates from the target service deployed in the first business system.

[0007] Read the target relationship mapping table established for the target service from at least one relationship mapping table in the anti-corrosion layer, and read the target general table established for the target service from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which is used to characterize the association between the first target business data and the target general data to be added to the target general table.

[0008] Based on the first storage relationship configuration information extracted from the target relationship mapping table, the first target business data is converted into target general data and then added to the target general table.

[0009] According to embodiments of this disclosure, storing newly added target general data into the target general table includes:

[0010] Add a new target data row to the target general table;

[0011] Store the target general data in the target data row.

[0012] According to embodiments of this disclosure, wherein:

[0013] The first storage relationship configuration information includes name configuration information, which is used to represent: the target general name of the target general data associated with the first target business data in the target general table;

[0014] Converting the primary target business data into target general data includes:

[0015] The values ​​of the target business fields are extracted from the first target business data, and the name configuration information is extracted from the first storage relationship configuration information. The values ​​of the target business fields are used to characterize the business meaning of the first target business data.

[0016] Based on the name configuration information, the target general data is generated by combining the values ​​of the target business fields with the target generic name.

[0017] According to embodiments of this disclosure, wherein:

[0018] The first target business data includes multiple original business fields corresponding to multiple data hierarchical structures. The first storage relationship configuration information includes original field configuration information, which is used to characterize: the target data hierarchy of the target business field to be extracted from the multiple original business fields in the first target business data.

[0019] The values ​​of the target business fields extracted from the first target business data include:

[0020] Extract the original field configuration information from the first storage relationship configuration information;

[0021] Based on the original field configuration information, extract the values ​​of the target business fields corresponding to the target data level from the first target business data.

[0022] According to embodiments of this disclosure, wherein:

[0023] The target relationship mapping table is also pre-configured with second storage relationship configuration information. The second storage relationship configuration information is used to characterize the relationship between the target general data and the second target business data to be added to the target business table. The target business table originates from the second business system.

[0024] The above methods also include:

[0025] Based on the second storage relationship configuration information extracted from the target relationship mapping table, the target general data is converted into second target business data;

[0026] Send the second target business data to the second business system so that the second business system can add and store the second target business data in the target business table.

[0027] According to embodiments of this disclosure, the second business system adding and storing the second target business data to the target business table includes performing the following operations through the second business system:

[0028] Add a target data column to the target business table;

[0029] Store the second target business data in the target data column.

[0030] According to embodiments of this disclosure, wherein:

[0031] The second storage relationship configuration information includes business field configuration information, which is used to characterize: the business field name corresponding to the second target business data associated with the target general data in the target business table;

[0032] The conversion of target general data into second target business data includes:

[0033] Extract the values ​​of target business fields from the target general data, and extract business field configuration information from the second storage relationship configuration information. The values ​​of the target business fields are used to characterize the business meaning of the first target business data.

[0034] Based on the business field configuration information, the value and name of the target business field are combined to generate the second target business data.

[0035] Another aspect of this disclosure provides a data storage device, including a calling module, a reading module, and a conversion storage module.

[0036] The calling module is used to respond to data calling requests by calling the first data interface associated with the first business system to obtain the first target business data to be stored from the first business system. The first target business data originates from the target service deployed in the first business system.

[0037] The reading module is used to read the target relationship mapping table established for the target service from at least one relationship mapping table in the anti-corrosion layer, and to read the target general table established for the target service from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which is used to characterize the association between the first target business data and the target general data to be added to the target general table.

[0038] The conversion storage module is used to convert the first target business data into target general data and then add it to the target general table based on the first storage relationship configuration information extracted from the target relationship mapping table.

[0039] According to embodiments of this disclosure, the conversion storage module includes a first newly added unit and a first storage unit.

[0040] The first new unit is used to add a target data row to the target general table; the first storage unit is used to store the target general data into the target data row.

[0041] According to an embodiment of this disclosure, the first storage relationship configuration information includes name configuration information, which is used to characterize the target general name of the target general data associated with the first target business data in the target general table.

[0042] The conversion and storage module includes a first extraction unit and a first generation unit.

[0043] The first extraction unit is used to extract the value of the target business field from the first target business data and extract the name configuration information from the first storage relationship configuration information. The value of the target business field is used to characterize the business meaning of the first target business data. The first generation unit is used to generate target general data by combining the value of the target business field and the target general name based on the name configuration information.

[0044] According to an embodiment of this disclosure, the first target business data includes multiple original business fields corresponding to multiple data hierarchical structures, and the first storage relationship configuration information includes original field configuration information, which is used to characterize the target data hierarchy of the target business field to be extracted from the multiple original business fields in the first target business data.

[0045] The extraction unit includes a first extraction subunit and a second extraction subunit.

[0046] The first extraction subunit is used to extract the original field configuration information from the first storage relationship configuration information; the second extraction subunit is used to extract the value of the target business field corresponding to the target data level from the first target business data based on the original field configuration information.

[0047] According to an embodiment of this disclosure, the target relationship mapping table is further pre-configured with second storage relationship configuration information. The second storage relationship configuration information is used to characterize the association between the target general data and the second target business data to be added to the target business table, and the target business table originates from the second business system.

[0048] The aforementioned device also includes a conversion module and a transmission module.

[0049] The conversion module is used to convert target general data into second target business data based on the second storage relationship configuration information extracted from the target relationship mapping table; the sending module is used to send the second target business data to the second business system so that the second business system can add the second target business data to the target business table.

[0050] According to embodiments of this disclosure, the sending module includes a second addition unit and a second storage unit.

[0051] The second newly added unit is used to add a target data column to the target business table through the second business system; the second storage unit is used to store the second target business data into the target data column through the second business system.

[0052] According to an embodiment of this disclosure, the second storage relationship configuration information includes business field configuration information, which is used to characterize the business field name corresponding to the second target business data associated with the target general data in the target business table.

[0053] The conversion module includes a second extraction unit and a second generation unit.

[0054] The second extraction unit is used to extract the value of the target business field from the target general data and extract the business field configuration information from the second storage relationship configuration information. The value of the target business field is used to characterize the business meaning of the first target business data. The second generation unit is used to generate the second target business data by combining the value of the target business field and the business field name based on the business field configuration information.

[0055] Another aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the data storage method described above.

[0056] Another aspect of this disclosure provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the data storage method described above.

[0057] Another aspect of this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the above-described data storage method.

[0058] According to the data storage method, apparatus, equipment, medium, and program products provided in this disclosure, a new anti-corrosion layer is established to achieve communication conversion and semantic isolation for service data interaction between multiple systems. Based on the anti-corrosion layer as an isolation layer, a universal table is created in the anti-corrosion layer to achieve universal storage of data between multiple systems. Furthermore, a new relational mapping table is created to store the mapping relationship between the universal data in the universal table and the original data of the data provider. On this basis, the original data of the data provider is first read through the anti-corrosion layer, and then, according to the relationship between the original data and the universal data in the relational mapping table, the original data is converted into universal data and stored in the universal table. The establishment of the universal table achieves universal storage of data between multiple systems, rather than being limited to the storage of data in a specific business scenario. Based on the universal storage table structure that is compatible with multiple service interfaces, data storage can be easily performed by combining the universal table with a data relationship mapping table. This breaks through the limitations of service granularity. Only one table creation and one development are needed to meet the needs of most storage scenarios. The relational configuration mode is compatible with multi-service data scenarios, which solves the problem of frequent database operations when calling different service interfaces to store data in scenarios with frequent data calls. It avoids frequent table modification operations when the data content of upstream and downstream interfaces changes, reduces the risks of frequent table creation and the complexity of using multiple tables, ensures the high availability of the system, and is fully and flexibly configurable to adapt to various scenarios, better assisting data interaction between systems. Attached Figure Description

[0059] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0060] Figure 1 The illustrations depict application scenarios of data storage methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0061] Figure 2 A flowchart illustrating a data storage method according to an embodiment of the present disclosure is shown schematically.

[0062] Figure 3 A schematic diagram of a system principle for a data storage method applicable to embodiments of the present disclosure is shown.

[0063] Figure 4 A schematic block diagram of a data storage device according to an embodiment of the present disclosure is shown; and

[0064] Figure 5 A block diagram schematically illustrates an electronic device suitable for implementing a data storage method according to an embodiment of the present disclosure. Detailed Implementation

[0065] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0066] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0067] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0068] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0069] In the embodiments disclosed herein, the collection, updating, analysis, processing, use, transmission, provision, disclosure, and storage of data (e.g., including but not limited to user personal information) comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. In particular, necessary measures have been taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0070] In the embodiments disclosed herein, user authorization or consent is obtained before acquiring or collecting user personal information.

[0071] With the continuous improvement of information services, data interaction between various business systems is becoming increasingly frequent. A complete closed loop of a business process requires querying and analyzing a large amount of relevant data to arrive at the correct conclusions. Storing relevant data not only facilitates rapid retrieval and use in business operations, but is also a crucial foundation for discovering related problems and generating data reports.

[0072] For scenarios involving data interaction between systems, the data processing methods in related technologies are typically tailored to specific scenarios. For example, the data caller may differentiate data storage from a business perspective (storing data in a business master table), where each business system typically stores the various service data retrieved in its own business master table. Alternatively, the data caller may differentiate data storage from a service perspective (each service has at least one data table), storing the data of the individual service retrieved in its corresponding data table. These methods are limited to specific scenarios, and every data change implies a modification to the storage structure, increasing the complexity of data storage and usage for the caller.

[0073] In view of the above, embodiments of this disclosure provide a data storage method, including:

[0074] In response to a data call request, the system retrieves first target business data to be stored from the first business system by calling a first data interface associated with the first business system. The first target business data originates from a target service deployed within the first business system. The system reads a target relationship mapping table established for the target service from at least one relationship mapping table in the anti-corrosion layer, and reads a target general table established for the target service from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which characterizes the association between the first target business data and the target general data to be added to the target general table. Based on the first storage relationship configuration information extracted from the target relationship mapping table, the first target business data is converted into target general data and then added to the target general table.

[0075] Figure 1 The illustrations depict application scenarios of data storage methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0076] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first business system 101, a second business system 102, an anti-corrosion layer 103, and a database 104. The first business system 101, the second business system 102, the anti-corrosion layer 103, and the database 104 can interact with each other via a network, which may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0077] The first business system 101 and the second business system 102 can be used to provide corresponding application services. They can consist of one or more servers. The servers can be servers that provide various services, such as a backend management server that supports websites browsed by users using terminal devices (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0078] The anti-corrosion layer 103 is a component or service built between the application itself and the outside world, used to perform communication conversion and semantic isolation for data interaction between the first business system 101 and the second business system 102.

[0079] In the application scenarios of this disclosure embodiment, there are scenarios where the first business system 101 and the second business system 102 need to call each other across services due to business needs. For example, the first business system 101 calls the data of the second business system 102, or the second business system 102 calls the data of the first business system 101.

[0080] The anti-corrosion layer 103 can be used to store the data being accessed. For example, in a scenario where the first business system 101 accesses data from the second business system 102, the anti-corrosion layer 103 can be used to first retrieve the data from the second business system 102 and store it in the form of general data (specifically, it can be stored in the database 104 connected to the anti-corrosion layer 103). Then, the first business system 101 can retrieve the data from the anti-corrosion layer 103. Similarly, in a scenario where the second business system 102 accesses data from the first business system 101, the anti-corrosion layer 103 can be used to first retrieve the data from the first business system 101 and store it in the form of general data (specifically, it can be stored in the database 104 connected to the anti-corrosion layer 103). Then, the second business system 102 can retrieve the data from the anti-corrosion layer 103.

[0081] It should be noted that the data storage method provided in this embodiment can generally be executed by the anti-corrosion layer 103. Accordingly, the data storage device provided in this embodiment can generally be disposed in the anti-corrosion layer 103. The anti-corrosion layer 103 can be disposed independently of the first business system 101 and the second business system 102, or it can be disposed inside the first business system 101 or inside the second business system 102.

[0082] It should be noted that the data storage methods, apparatus, devices, media, and program products of this disclosure can be used in the field of big data technology, the field of financial technology, or any field other than the field of big data technology and the field of financial technology. The embodiments of this disclosure do not limit the application fields of the above-mentioned data storage methods, apparatus, devices, media, and program products.

[0083] The following will be based on Figure 1 The described scene, through Figures 2-5 The data storage method of the disclosed embodiments will be described in detail.

[0084] Figure 2 A flowchart illustrating a data storage method according to an embodiment of the present disclosure is shown schematically.

[0085] like Figure 2 As shown, the data storage method of this embodiment includes operations S201 to S203.

[0086] In operation S201, in response to a data call request, the first target business data to be stored is obtained from the first business system by calling the first data interface associated with the first business system. The first target business data originates from the target service deployed in the first business system.

[0087] In operation S202, a target relationship mapping table established for the target service is read from at least one relationship mapping table in the anti-corrosion layer, and a target general table established for the target service is read from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which is used to characterize the association between the first target business data and the target general data to be added to the target general table.

[0088] In operation S203, based on the first storage relationship configuration information extracted from the target relationship mapping table, the first target business data is converted into target general data and then added to the target general table.

[0089] Figure 3 A schematic diagram of a system principle to which embodiments of the present disclosure can be applied is shown.

[0090] like Figure 3 As shown, in scenarios involving cross-system data access, the system to which the data storage method of this disclosure embodiment can be applied may include multiple business systems, such as, but not limited to, [other systems]. Figure 3The diagram shows a first business system (System 1), a second business system (System 2), and an anti-corrosion layer. Multiple business systems can be used to provide different application services and generate corresponding business data within their respective systems. For example, the first business system includes service A and service B, which respectively generate business data A and business data B.

[0091] In the application scenarios of this disclosure embodiment, there are scenarios where the first business system and the second business system need to call each other across services due to business needs. For example, the first business system calls the data of the second business system, or the second business system calls the data of the first business system.

[0092] The anti-corrosion layer is a component or service built between the application itself and the external environment, used to perform communication conversion and semantic isolation for data interaction between the first business system and the second business system. In the data storage method of this disclosure embodiment, the anti-corrosion layer can be used as a general data retrieval and storage structure. The anti-corrosion layer can be used to store the retrieved data, for example, such as... Figure 3 In the scenario shown where the second business system calls data from the first business system, the data can first be obtained from the first business system through the anti-corrosion layer and stored in the anti-corrosion layer in the form of general data (specifically, it can be stored in a database connected to the anti-corrosion layer), and then the second business system can obtain the data from the anti-corrosion layer.

[0093] According to embodiments of this disclosure, the data provider (such as...) Figure 3 In the system 1) shown, data can be provided to the outside world through encapsulated data interfaces. Each application service can have its own data interface, such as... Figure 3 As shown, data A is generated by providing service A through interface A, and data B is generated by providing service B through interface B.

[0094] According to embodiments of this disclosure, a service interface can be added to the anti-corrosion layer for data callers to invoke. The anti-corrosion layer is set up as an independent service unit, and it provides the retrieved data to each data caller in the form of a service interface. For example... Figure 3 As shown, the data caller can obtain data from the general table through the anti-corrosion layer's interfaces A1 and B1.

[0095] Furthermore, after the anti-corrosion layer obtains data from the data provider by calling the data interface, it can perform general processing (such as conversion of general data formats, processing of general business logic, etc.) within the anti-corrosion layer.

[0096] According to embodiments of this disclosure, at least one general table and at least one relational mapping table can be pre-created in the anti-corrosion layer. The general table and relational mapping table are established based on the service dimension, targeting different services of the data provider. For example, different general tables and relational mapping tables are created for service A and service B, respectively. The general table stores the interface data information to be saved, stored in the form of general data. The relational mapping table stores the mapping relationships between the general data and the original data of the data provider.

[0097] According to embodiments of this disclosure, based on Figure 3 The system architecture shown below, with the second business system as the data caller and the first business system as the data provider, will be used as an example in the following discussion. Figure 2 , Figure 3 The above operations S201 to S203 will be further explained.

[0098] According to embodiments of this disclosure, the anti-corrosion layer can be used to perform two operations: data storage (storing data from the data provider in a general table) and data retrieval (reading data already stored in the general table and providing it to the data caller). Operations S201 to S203 described above use the anti-corrosion layer as the execution entity to perform the aforementioned data storage operations.

[0099] Specifically, the above operation S201 may be: the anti-corrosion layer responds to the data caller - the second business system's data call request, and obtains the first target business data to be stored from the first business system by calling the first data interface provided by the first business system.

[0100] The first data interface provided to the outside world by the first business system can be, for example, Figure 3 The interface A or interface B shown depends on the service corresponding to the data called by the data caller. The first target business data is the data that the data caller wants to call, which can be data A or data B. Data A originates from service A deployed in the first business system, and data B originates from service B deployed in the first business system.

[0101] The data call request includes a service name field. The anti-corruption layer parses the data call request to determine the first data interface corresponding to the data to be called by the data caller. It then retrieves the first target business data to be stored from the first business system by calling the first data interface. For example, by parsing the data call request, it determines that the business data to be called is "Service A" (corresponding to the service name field in the data call request) in System 1, and further determines the interface A corresponding to Service A. From interface A, it obtains the first target business data to be stored: Data A.

[0102] Specifically, the above operation S202 can be: based on the service name field included in the data call request, a target relationship mapping table established for the target service can be read from at least one relationship mapping table in the anti-corruption layer; and a target general table established for the target service can be read from at least one general table in the anti-corruption layer. The relationship mapping table is used to store the mapping relationship between general data in the general table and the original data of the data provider. Specifically, the first storage relationship configuration information pre-configured in the target relationship mapping table is used to characterize the relationship between the first target business data (the original data of the data provider) and the target general data to be added to the target general table.

[0103] Furthermore, based on the pre-established relational mapping table, in operation S203, the first target business data can be converted into target general data and then added to the target general table based on the first storage relational configuration information extracted from the target relational mapping table.

[0104] In related technologies, various business systems store the multiple service data retrieved in their own business master tables, or store the data of a single service retrieved in its corresponding data table. Because the data tables are stored in their respective business systems, each data field in the data table within the system needs to have a clear business meaning in order to facilitate system use. A general data table structure cannot be used. Therefore, every change in data means a modification to the storage structure. Moreover, as business data continues to increase, the width of the business data table will become very large, or it will be necessary to frequently create new data tables to store the newly added data, which presents many problems.

[0105] In contrast, the method of this disclosure achieves communication conversion and semantic isolation for service data interaction between multiple systems by creating a new anti-corrosion layer. Based on the anti-corrosion layer as an isolation layer, a universal table is created within the anti-corrosion layer to achieve universal data storage across multiple systems. Furthermore, a new relational mapping table is created to store the mapping relationship between the universal data in the universal table and the original data from the data provider. Based on this, operations S201 to S203 are performed through the anti-corrosion layer. First, the original data from the data provider is read. Then, based on the relationship between the original data and the universal data in the relational mapping table, the original data is converted into universal data and stored in the universal table. The establishment of the universal table achieves universal data storage across multiple systems, rather than being limited to data storage in a specific business scenario. Based on the universal storage table structure that is compatible with multiple service interfaces, data storage can be easily performed by combining the universal table with a data relationship mapping table. This breaks through the limitations of service granularity. Only one table creation and one development are needed to meet the needs of most storage scenarios. The relational configuration mode is compatible with multi-service data scenarios, which solves the problem of frequent database operations when calling different service interfaces to store data in scenarios with frequent data calls. It avoids frequent table modification operations when the data content of upstream and downstream interfaces changes, reduces the risks of frequent table creation and the complexity of using multiple tables, ensures the high availability of the system, and is fully and flexibly configurable to adapt to various scenarios, better assisting data interaction between systems.

[0106] According to embodiments of this disclosure, further storing the target general data in the target general table may specifically include the following operations:

[0107] First, add a new target data row to the target general table.

[0108] Next, the target general data is stored in the target data row.

[0109] Table 1 below is an example of table structure information in a general table.

[0110] Table 1

[0111]

[0112] As shown in Table 1, the primary key of the general table example consists of a unique identifier for each business transaction – the business number – plus the corresponding service name field, indicating which business service the general table is created for. It also includes common fields such as creation time, modification time, service response, return code, and return description. Additionally, it includes general data derived from the first business data (originating from the original business data of the first business system). For example, the VARCHAR2 (4000) string fields of type DATA1 to DATA50 in the table serve as general fields for storing business data, used to store the actual response results of the storage data. The number of these fields can be customized by the user according to their needs.

[0113] As shown in Table 1, the general data in the general table does not have specific business meaning and is only distinguished by the general name field.

[0114] Taking Table 1 as an example, based on the existing general book containing DATA1 to DATA50, the target general data is added and stored in the target general table. For example, a new target data row DATA51 can be added to the target general table; and the target general data is stored in the target data row represented by DATA51.

[0115] Table 2 shows an example of the table structure of business tables within the business system.

[0116] Table 2

[0117] Business Number Service Name Creation time …… Data 1 Data 2 Data 3 …… BUSINO MOUDLE CREATETIME …… DATA1 DATA2 DATA3 …… 123456789 CCDSRISK 2022-8-28 …… Loan Account Loan amount Loan date ……

[0118] As shown in Table 2, because the data tables in these related technologies are stored in their respective business systems, each data field in the system's data tables needs to have a clear business meaning for ease of use, such as the data fields "Price Account," "Loan Amount," and "Loan Date" in Table 2. A general data table structure cannot be used. Therefore, whenever new business field data is obtained from an external system, new data fields need to be added. As a result, with the continuous increase in business data, the width of the business data tables will become very large, and a large number of redundant and useless fields will be retained in the business tables, increasing the complexity of subsequent data storage, data cleaning, and data retrieval.

[0119] In contrast, storing data in a general table, where data is stored as newly added rows, avoids increasing the table's width and simplifies the data storage structure. This makes the general table suitable for general data storage. Furthermore, when external data-receiving systems retrieve data from the general table, they can selectively obtain only the necessary information. This avoids a large number of redundant and useless fields in the business tables, improving the efficiency of data processing for data-receiving systems and simplifying the data storage structure.

[0120] According to an embodiment of this disclosure, in the relationship mapping table, the first storage relationship configuration information includes name configuration information, which is used to characterize the target general name of the target general data associated with the first target business data in the target general table.

[0121] Table 3 shows an example of the table structure information for a relational mapping table.

[0122] Table 3

[0123]

[0124] As shown in the example of the relational mapping table in Table 3, the primary key ID can be composed of a service name plus an incrementing number. The "service name" identifies which business service the general table is created for, and the "incrementing number" indicates how many data mapping relationships are configured under that business service. The name configuration information is shown in the DB_FIELD row of Table 3, corresponding to the DATA[n] field in the general table. This field represents the general name of the general data in the general table (e.g., DATA1 to DATA50 in Table 1). The table also contains common fields such as creation time.

[0125] Based on this, the conversion of the first target business data into target general data includes:

[0126] First, the values ​​of the target business fields are extracted from the first target business data, and the name configuration information is extracted from the first storage relationship configuration information. The values ​​of the target business fields are used to represent the business meaning of the first target business data. Because the raw business data returned by the data provider is usually in JSON data format with hierarchical relationships, it is necessary to obtain the values ​​of the target business fields that represent the business meaning of the first target business data by parsing the first target business data (raw business data).

[0127] Next, based on the name configuration information, the target general data is generated by combining the value of the target business field with the target generic name. For example, by reading the value corresponding to DB_FIELD from the relationship mapping table shown in Table 3, and finding that the target general name corresponding to the target general data in the target general table is "DATA52", the target general data is obtained by combining "DATA52" with the value of the target business field.

[0128] Furthermore, in the scenario of adding new data to the general table, a new target data row DATA52 is added to the target general table; and the target general data is stored in the target data row represented by DATA52.

[0129] According to embodiments of this disclosure, by configuring name configuration information in the relationship mapping table, the original business data of the data provider and the general data in the general table are associated. The general data in the general table does not have specific business meaning and is only distinguished by the general name field, thus realizing the general storage of business data in the anti-corrosion layer.

[0130] According to embodiments of this disclosure, since the first target business data (raw business data) returned by the data provider is typically in a hierarchical JSON data format, the first target business data includes multiple raw business fields corresponding to multiple data hierarchical structures. It is necessary to parse the first target business data (raw business data) to obtain the values ​​of the target business fields used to characterize the business meaning of the first target business data.

[0131] As shown in the relation mapping table example in Table 3, the first storage relation configuration information also includes original field configuration information. This original field configuration information, as shown in the ORGDATA_MAPPING row of Table 3, represents the target data level of the target business field to be extracted from multiple original business fields in the first target business data. For example, the original field configuration information can have a structure similar to ABC, where level C represents the actual level of the target business field.

[0132] Based on this, the values ​​of the target business fields extracted from the first target business data include:

[0133] Extract the original field configuration information from the first storage relationship configuration information. For example, read the value of ORGDATA_MAPPING from the relationship mapping table shown in Table 3, such as datal.Information.Name.

[0134] Based on the original field configuration information, the values ​​of the target business fields corresponding to the target data level are extracted from the first target business data. For example, based on the read original field configuration information: data1.Information.Name, the value of the target business field to be extracted is determined to be the value corresponding to the "Name" field. Among the multiple original business fields of the first target business data: "Data-Information-Zhang San", "Zhang San" is extracted as the value of the target business field.

[0135] According to embodiments of this disclosure, based on Figure 3 The system architecture shown takes the second business system as the data caller and the first business system as the data provider as an example. Figure 3As shown, in cross-system component data retrieval scenarios, the anti-corruption layer can be used to perform two operations: data storage (storing the data provider's data in a general table) and data retrieval (reading the data already stored in the general table and providing it to the data caller). Operations S201 to S203 described above are data storage operations in the anti-corruption layer that convert data originating from the first business system into general data stored in a general table. The following describes the data retrieval operation where the anti-corruption layer converts general data into business data suitable for the second business system and provides it to the second business system.

[0136] Specifically, the target relationship mapping table is also pre-configured with second storage relationship configuration information. The second storage relationship configuration information is used to characterize the relationship between the target general data and the second target business data to be added to the target business table. The target business table originates from the second business system.

[0137] Based on this, the above-mentioned data reading operations include:

[0138] First, based on the second storage relationship configuration information extracted from the target relationship mapping table, the target general data is converted into second target business data. For example, if the target general table is a general table A established for a service, the data caller—the second business system—can read data from the general table A through the anti-corruption layer interface A1 (corresponding to the general table A) and store it in the business table A within the second business system. Then, based on the association between the general data in the general table A and the second target business data to be added to the target business table (business table A), the general data in the general table A is converted into second target business data.

[0139] Then, the second target business data is sent to the second business system so that the second business system can add the second target business data to the target business table, for example, to business table A in the system.

[0140] According to the embodiments of this disclosure, when a data caller retrieves data from a general table, the specific business meaning of the general data must be clearly defined before it can be used internally by the system. By pre-configuring the association between the general data and the data to be added to the business table in the relationship mapping table, the general data can be converted into data with specific business meaning and sent to the data caller, thus achieving the purpose of the data caller retrieving the corresponding data.

[0141] According to embodiments of this disclosure, specifically, the second storage relationship configuration information includes business field configuration information, which is used to characterize the business field name corresponding to the second target business data associated with the target general data in the target business table. As shown in the relationship mapping table example in Table 3, the business field configuration information is represented by the EXTDATA_MAPPING row in Table 3, and the value of the EXTDATA_MAPPING row corresponds to the field name that the anti-corrosion layer data interface intends to return to the data caller. As shown in the relationship mapping table example in Table 3, the business field configuration information may also include the DATA_TYPE row in Table 3, and the value of the DATA_TYPE row corresponds to the field type that the anti-corrosion layer data interface intends to return to the data caller.

[0142] Based on this, the conversion of target general data into second target business data includes:

[0143] First, the values ​​of the target business fields are extracted from the target general data, and the business field configuration information is extracted from the second storage relationship configuration information. The values ​​of the target business fields are used to represent the business meaning of the first target business data. The target general data is transformed from the first target business data (originating from the original business data of the first business system). Specifically, the target general data is generated by combining the values ​​of the target business fields with the target general name. Only the data format is changed during the transformation process; the actual business data is retained. Therefore, both the target general data and the first target business data retain the values ​​of the target business fields used to represent the business meaning of the first target business data. Here, the values ​​of these target business fields are extracted first.

[0144] Next, based on the business field configuration information, the values ​​and names of the target business fields are combined to generate the second target business data. The business field configuration information is pre-configured and represents the name of the corresponding business field in the target business table for the second target business data associated with the target general data. This name represents the specific business meaning; for example, it could be a name like "Name" or "Loan Amount." The values ​​of the target business fields are the specific field values, such as "Zhang San" or "5000 Yuan." The second target business data is generated by combining the values ​​and names of the target business fields; for example, combining "Name" and "Zhang San" generates one set of data, and combining "Loan Amount" and "5000 Yuan" generates another set.

[0145] According to embodiments of this disclosure, the above method enables the conversion of general data into data with specific business meaning, so that the data caller can use the business data to perform business processing.

[0146] Furthermore, after obtaining the second target business data, the second target business data is sent to the second business system, so that the second business system adds and stores the second target business data to the target business table, for example, to business table A within the system. Specifically, this could be:

[0147] First, add a target data column to the target business table;

[0148] Then, the second target business data is stored in the target data column.

[0149] For example, referring to the table structure example of the target business table in the business system shown in Table 2, in order to facilitate data processing within the system, each column of data in the business table needs to have a clear business meaning for its corresponding business field, such as the data fields "Price Account", "Loan Amount", and "Loan Date" in Table 2.

[0150] Adding a new target data column in the target business table can be done by adding a new target data column corresponding to the business field "Data 4 - Repayment Date", and storing the second target business data "Repayment Date - 2022-05-01" in this column.

[0151] According to embodiments of this disclosure, by adding new stored data in the business table within the data caller system in the form of new columns (each column corresponds to a business field), the specific business meaning of each piece of data can be reflected, so as to achieve the purpose of using business data to realize business processing.

[0152] Based on the above data storage method, this disclosure also provides a data storage device. The following will be combined with... Figure 4 The device is described in detail.

[0153] Figure 4 A schematic block diagram of a data storage device according to an embodiment of the present disclosure is shown.

[0154] like Figure 4 As shown, the data storage 400 in this embodiment includes a calling module 401, a reading module 402, and a conversion storage module 403.

[0155] The calling module 401 is used to respond to a data calling request by calling the first data interface associated with the first business system to obtain the first target business data to be stored from the first business system. The first target business data originates from the target service deployed in the first business system.

[0156] The reading module 402 is used to read a target relationship mapping table established for the target service from at least one relationship mapping table in the anti-corrosion layer, and to read a target general table established for the target service from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which is used to characterize the association between the first target business data and the target general data to be added to the target general table.

[0157] The conversion storage module 403 is used to convert the first target business data into target general data and then add it to the target general table based on the first storage relationship configuration information extracted from the target relationship mapping table.

[0158] According to embodiments of this disclosure, the anti-corrosion layer can realize communication conversion and semantic isolation for service data interaction between multiple systems. Based on the anti-corrosion layer as an isolation layer, a general table within the anti-corrosion layer can realize the general storage of data between multiple systems. Furthermore, a relational mapping table is used to store the mapping relationship between the general data in the general table and the original data of the data provider. On this basis, by calling module 401, the original data of the data provider is first read. Then, by reading module 402 and conversion storage module 403, the original data is converted into general data and stored in the general table according to the relationship between the original data and the general data in the relational mapping table. This realizes the general storage of data between multiple systems, rather than being limited to the storage of data in a certain business scenario. Based on the universal storage table structure that is compatible with multiple service interfaces, data storage can be easily performed by combining the universal table with a data relationship mapping table. This breaks through the limitations of service granularity. Only one table creation and one development are needed to meet the needs of most storage scenarios. The relational configuration mode is compatible with multi-service data scenarios, which solves the problem of frequent database operations when calling different service interfaces to store data in scenarios with frequent data calls. It avoids frequent table modification operations when the data content of upstream and downstream interfaces changes, reduces the risks of frequent table creation and the complexity of using multiple tables, ensures the high availability of the system, and is fully and flexibly configurable to adapt to various scenarios, better assisting data interaction between systems.

[0159] According to embodiments of this disclosure, the conversion storage module includes a first newly added unit and a first storage unit.

[0160] The first new unit is used to add a target data row to the target general table; the first storage unit is used to store the target general data into the target data row.

[0161] According to an embodiment of this disclosure, the first storage relationship configuration information includes name configuration information, which is used to characterize the target general name of the target general data associated with the first target business data in the target general table.

[0162] The conversion and storage module includes a first extraction unit and a first generation unit.

[0163] The first extraction unit is used to extract the value of the target business field from the first target business data and extract the name configuration information from the first storage relationship configuration information. The value of the target business field is used to characterize the business meaning of the first target business data. The first generation unit is used to generate target general data by combining the value of the target business field and the target general name based on the name configuration information.

[0164] According to an embodiment of this disclosure, the first target business data includes multiple original business fields corresponding to multiple data hierarchical structures, and the first storage relationship configuration information includes original field configuration information, which is used to characterize the target data hierarchy of the target business field to be extracted from the multiple original business fields in the first target business data.

[0165] The extraction unit includes a first extraction subunit and a second extraction subunit.

[0166] The first extraction subunit is used to extract the original field configuration information from the first storage relationship configuration information; the second extraction subunit is used to extract the value of the target business field corresponding to the target data level from the first target business data based on the original field configuration information.

[0167] According to an embodiment of this disclosure, the target relationship mapping table is further pre-configured with second storage relationship configuration information. The second storage relationship configuration information is used to characterize the association between the target general data and the second target business data to be added to the target business table, and the target business table originates from the second business system.

[0168] The aforementioned device also includes a conversion module and a transmission module.

[0169] The conversion module is used to convert target general data into second target business data based on the second storage relationship configuration information extracted from the target relationship mapping table; the sending module is used to send the second target business data to the second business system so that the second business system can add the second target business data to the target business table.

[0170] According to embodiments of this disclosure, the sending module includes a second addition unit and a second storage unit.

[0171] The second newly added unit is used to add a target data column to the target business table through the second business system; the second storage unit is used to store the second target business data into the target data column through the second business system.

[0172] According to an embodiment of this disclosure, the second storage relationship configuration information includes business field configuration information, which is used to characterize the business field name corresponding to the second target business data associated with the target general data in the target business table.

[0173] The conversion module includes a second extraction unit and a second generation unit.

[0174] The second extraction unit is used to extract the value of the target business field from the target general data and extract the business field configuration information from the second storage relationship configuration information. The value of the target business field is used to characterize the business meaning of the first target business data. The second generation unit is used to generate the second target business data by combining the value of the target business field and the business field name based on the business field configuration information.

[0175] According to embodiments of this disclosure, any plurality of modules among the calling module 401, reading module 402, and conversion storage module 403 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the calling module 401, reading module 402, and conversion storage module 403 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the calling module 401, reading module 402, and conversion storage module 403 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0176] Figure 5 A block diagram schematically illustrates an electronic device suitable for implementing a data storage method according to an embodiment of the present disclosure.

[0177] like Figure 5As shown, an electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage portion 508 into a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0178] RAM 503 stores various programs and data required for the operation of electronic device 500. Processor 501, ROM 502, and RAM 503 are interconnected via bus 504. Processor 501 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 502 and / or RAM 503. It should be noted that the programs may also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0179] According to embodiments of this disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to a bus 504. The electronic device 500 may also include one or more of the following components connected to the I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 510 as needed so that computer programs read from it can be installed into the storage section 508 as needed.

[0180] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0181] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 502 and / or RAM 503 and / or one or more memories other than ROM 502 and RAM 503 described above.

[0182] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the data storage method provided in the embodiments of this disclosure.

[0183] When the computer program is executed by the processor 501, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0184] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 509, and / or installed from a removable medium 511. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0185] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by processor 501, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0186] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0187] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0188] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0189] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A data storage method, applied to an anti-corrosion layer between a first business system and a second business system, comprising: The anti-corrosion layer is used to perform the following operations: converting data originating from the first business system into general data stored in a general table within the anti-corrosion layer, and converting general data into business data suitable for the second business system for data reading operations provided to the second business system. The data storage operation includes: In response to a data call request, the system retrieves first target business data to be stored from the first business system by calling a first data interface associated with the first business system, wherein the first target business data originates from a target service deployed in the first business system. From at least one relation mapping table in the anti-corrosion layer, a target relation mapping table established for the target service is read, and from at least one general table in the anti-corrosion layer, a target general table established for the target service is read. The target relation mapping table is pre-configured with first storage relation configuration information, which characterizes the association between the first target business data and the target general data to be added to the target general table. The general data in the general table does not have specific business meaning; the business data is stored generically in the anti-corrosion layer, and the general table has a generic storage table structure compatible with multiple service interfaces. Based on the first storage relationship configuration information extracted from the target relationship mapping table, the first target business data is converted into the target general data and then newly stored in the target general table; The data reading operation includes: Based on the second storage relationship configuration information extracted from the target relationship mapping table, the target general data is converted into second target business data; the second target business data is sent to the second business system so that the second business system adds the second target business data to the target business table of the second business system; wherein, the second storage relationship configuration information is used to characterize the association relationship between the target general data and the second target business data to be added to the target business table.

2. The method according to claim 1, wherein, Adding and storing the target general data to the target general table includes: Add a new target data row to the target general table; The target general data is stored in the target data row.

3. The method according to claim 1, wherein: The first storage relationship configuration information includes name configuration information, which is used to characterize the target general name of the target general data associated with the first target business data in the target general table; Converting the first target business data into the target general data includes: The value of the target business field is extracted from the first target business data, and the name configuration information is extracted from the first storage relationship configuration information. The value of the target business field is used to characterize the business meaning of the first target business data. Based on the name configuration information, the target general data is generated by combining the value of the target business field with the target generic name.

4. The method according to claim 3, wherein: The first target business data includes multiple original business fields corresponding to multiple data hierarchical structures. The first storage relationship configuration information also includes original field configuration information, which is used to characterize the target data level of the target business field to be extracted from the multiple original business fields in the first target business data. Extracting the values ​​of the target business fields from the first target business data includes: Extract the original field configuration information from the first storage relationship configuration information; Based on the original field configuration information, the value of the target business field corresponding to the target data level is extracted from the first target business data.

5. The method according to claim 1, wherein, The second business system adds and stores the second target business data to the target business table, including performing the following operations through the second business system: Add a target data column to the target business table; The second target business data is stored in the target data column.

6. The method according to claim 1, wherein: The second storage relationship configuration information includes business field configuration information, which is used to characterize: the business field name corresponding to the second target business data associated with the target general data in the target business table; Converting the target general data into the second target business data includes: The values ​​of target business fields are extracted from the target general data, and the business field configuration information is extracted from the second storage relationship configuration information. The values ​​of the target business fields are used to characterize the business meaning of the first target business data. Based on the business field configuration information, the value of the target business field and the name of the business field are combined to generate the second target business data.

7. A data storage device is applied to an anti-corrosion layer between a first business system and a second business system. The data storage device is used for data storage operations that convert data originating from the first business system into general data stored in a general table in the anti-corrosion layer, and for data reading operations that convert general data into business data suitable for the second business system and provide it to the second business system. The data storage device includes: The calling module is used to respond to a data calling request by calling a first data interface associated with the first business system to obtain the first target business data to be stored from the first business system, wherein the first target business data originates from the target service deployed in the first business system; The reading module is used to read a target relationship mapping table established for the target service from at least one relationship mapping table in the anti-corrosion layer, and to read a target general table established for the target service from at least one general table in the anti-corrosion layer. The target relationship mapping table is pre-configured with first storage relationship configuration information, which characterizes the association between the first target business data and the target general data to be added to the target general table. The general data in the general table does not have specific business meaning; the business data is stored universally in the anti-corrosion layer, and the general table has a universal storage table structure compatible with multiple service interfaces. The conversion storage module is used to convert the first target business data into the target general data and then add it to the target general table based on the first storage relationship configuration information extracted from the target relationship mapping table; The conversion module is used to convert target general data into second target business data based on the second storage relationship configuration information extracted from the target relationship mapping table; wherein, the second storage relationship configuration information is used to characterize the association relationship between the target general data and the second target business data to be added to the target business table; The sending module is used to send the second target business data to the second business system, so that the second business system can add the second target business data to the target business table.

8. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images