Data processing method, device, equipment, device and program product

Abstract

The embodiment of the invention relates to a budget processing method and device, equipment, a device and a program product. The method comprises the steps of receiving a data adjustment request; the data adjustment request comprises a target data identifier and a target adjustment value; determining a target adjustment mode adaptive to the target data identifier from a plurality of data adjustment modes; the data adjustment mode comprises a near-end deployed atomic adjustment mode based on a memory database, a transaction adjustment mode based on a first relational database or a distributed adjustment mode based on cooperation of the memory database and the first relational database; and based on the target data identifier and the target adjustment value, executing data adjustment processing corresponding to the target adjustment mode, and generating a data adjustment result. In this way, a more suitable data adjustment mode can be automatically decided, and the accuracy and efficiency of data management in a corresponding service scene are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of information processing technology, and in particular to a data processing method, apparatus, device, device, and program product. Background Art

[0002] Data management systems are used to efficiently manage various types of data. Leveraging the high-performance query and update capabilities of in-memory databases, many data management systems are currently implemented based on them. The core concept of this implementation is to store data identifiers in the in-memory database and perform data adjustments through direct data interaction with the in-memory database. However, this implementation is primarily suitable for data management scenarios requiring high performance and high concurrency, and is less applicable to other scenarios, resulting in poor data management capabilities. Summary of the Invention

[0003] In order to solve the above technical problems, the embodiments of the present disclosure provide a data processing method, apparatus, device, device and program product.

[0004] In a first aspect, an embodiment of the present disclosure provides a data processing method, the method comprising:

[0005] receiving a data adjustment request; wherein the data adjustment request includes a target data identifier and a target adjustment value;

[0006] Determining a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes; wherein the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on collaboration between the memory database and the first relational database;

[0007] Based on the target data identifier and the target adjustment value, a data adjustment process corresponding to the target adjustment mode is performed to generate a data adjustment result.

[0008] In a second aspect, an embodiment of the present disclosure provides a data processing method, the method comprising:

[0009] generating an initial data identifier in response to a received data creation request; wherein the data creation request includes a target data value;

[0010] Creating configuration data corresponding to the initial data identifier in the general data table based on the target data value;

[0011] Based on the initial data identifier, the data synchronization request table corresponding to the user client is queried, and when it is determined through the data synchronization request table that the initial data identifier is not idempotent, a target adjustment mode adapted to the initial data identifier is determined from multiple data adjustment modes; wherein the data synchronization request table is used to record the data identifier, configuration data and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed at the near end, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on the collaboration between the memory database and the second relational database;

[0012] The target data table corresponding to the target adjustment mode is updated using the initial data identifier and the configuration data corresponding to the initial data identifier.

[0013] In a third aspect, an embodiment of the present disclosure further provides a data processing device, the device comprising:

[0014] A request receiving module, configured to receive a data adjustment request; wherein the data adjustment request includes a target data identifier and a target adjustment value;

[0015] A first adjustment mode determination module is configured to determine a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes; wherein the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on a collaboration between the memory database and the first relational database;

[0016] The data adjustment module is configured to execute data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value, and generate a data adjustment result.

[0017] In a fourth aspect, an embodiment of the present disclosure further provides a data processing device, the device comprising:

[0018] an initial data identifier generating module, configured to generate an initial data identifier in response to a received data creation request; wherein the data creation request includes a target data value;

[0019] A configuration data creation module, configured to create configuration data corresponding to the initial data identifier in the general data table based on the target data value;

[0020] A second adjustment mode determination module is configured to query a data synchronization request table corresponding to the user client based on the initial data identifier, and when determining through the data synchronization request table that the initial data identifier is not idempotent, determine a target adjustment mode that is adapted to the initial data identifier from a plurality of data adjustment modes; wherein the data synchronization request table is configured to record the data identifier, configuration data, and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on collaboration between the memory database and the second relational database;

[0021] The target data table updating module is configured to update the target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier.

[0022] In a fifth aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising:

[0023] processor;

[0024] a memory for storing executable instructions;

[0025] The processor is used to read executable instructions from the memory and execute the executable instructions to implement the data processing method described in any embodiment of the present disclosure.

[0026] In a sixth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the data processing method described in any embodiment of the present disclosure.

[0027] In a seventh aspect, an embodiment of the present disclosure further provides a computer program product, which is used to execute the data processing method described in any embodiment of the present disclosure.

[0028] The data processing methods, devices, equipment, apparatus and program products of the embodiments of the present disclosure are capable of receiving a data adjustment request including a target data identifier and a target adjustment value; determining a target adjustment mode adapted to the target data identifier from among an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, and a distributed adjustment mode based on collaboration between the memory database and the first relational database; executing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result; and realizing automatic decision-making on a more suitable data adjustment mode based on the target data identifier, so that the system's data adjustment service can be more flexibly applied to various data adjustment scenarios, thereby improving the accuracy and efficiency of data adjustment in corresponding business scenarios and enhancing the system's data management capabilities.

[0029] The data processing methods, apparatuses, devices, devices, and program products of the disclosed embodiments are capable of generating an initial data identifier in response to a received data creation request including a target data value; creating configuration data corresponding to the initial data identifier in a general data table based on the target data value; querying a data synchronization request table corresponding to a user client based on the initial data identifier, and determining, through the data synchronization request table, a target adjustment mode adapted to the initial data identifier when determining that the initial data identifier is not idempotent; wherein the data synchronization request table is used to record the data identifier, configuration data, and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transactional adjustment mode based on a second relational database, or a distributed adjustment mode based on collaboration between a memory database and a second relational database; updating a target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier; achieving creation of data to be managed, and performing data consistency-based data synchronization on data tables corresponding to different data adjustment modes during the data creation process, thereby improving the efficiency and accuracy of data creation, providing a good data foundation for accurate data adjustment in subsequent different business scenarios, and further enhancing the data management capabilities of the system.

[0030] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present disclosure are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0032] Figure 1 A schematic diagram of a data interaction process of a data management system in related technology;

[0033] Figure 2 A schematic diagram of an access process of a data management system provided in an embodiment of the present disclosure;

[0034] Figure 3 A flowchart of a data processing method provided in an embodiment of the present disclosure;

[0035] Figure 4 A schematic diagram of a data interaction process for data synchronization provided by an embodiment of the present disclosure;

[0036] Figure 5 A flowchart of another data processing method provided by an embodiment of the present disclosure;

[0037] Figure 6 A flowchart of another data processing method provided in an embodiment of the present disclosure;

[0038] Figure 7 A schematic diagram of a flow chart of data incremental processing in a data processing method provided in an embodiment of the present disclosure;

[0039] Figure 8 A schematic structural diagram of a data processing device provided in an embodiment of the present disclosure;

[0040] Figure 9 A schematic structural diagram of another data processing device provided in an embodiment of the present disclosure;

[0041] Figure 10 A schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0042] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0043] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0044] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0045] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0046] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0047] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0048] In related technologies, data management systems are implemented based on in-memory databases, leveraging the high-performance query and update capabilities of in-memory databases. Figure 1 As shown, the user client accesses the data adjustment service provided by the data management system through a remote call. The data management system pre-stores relevant information of the data to be managed (such as data identification, total data value, etc.). After receiving the data adjustment request sent by the user client, the data management system directly interacts with the in-memory database to perform data adjustment processing. Then, the data management system can periodically write back the data usage asynchronously to the relational database for data backup. Although this data management solution can achieve high concurrency and high performance data adjustment, it lacks flexible support for diversified business scenarios. For example, this solution is mainly suitable for high-concurrency and high-performance data business scenarios, and its applicability to data business scenarios with high consistency, high traffic, etc. is poor. In these data business scenarios, the data processing efficiency and data processing accuracy of the above solution will be greatly reduced.

[0049] Based on the above situation, the present disclosure provides a data processing method, such as Figure 2 As shown, it can analyze the data adjustment request sent by the user client to determine the appropriate target adjustment mode, and then call the corresponding data adjustment service through the data adjustment service call method corresponding to the target adjustment mode to perform data adjustment processing. In this way, there is no need to develop additional data processing solutions, and data adjustment services that are more suitable for data business scenarios can be used to quickly perform data adjustment processing, which greatly improves the flexible applicability to diversified business scenarios, thereby improving data processing efficiency and accuracy.

[0050] The data processing method provided in the embodiments of the present disclosure is applicable to various scenarios involving data management via online services, and is particularly applicable to scenarios where data adjustments are triggered by user clients through access requests. The method can be executed by a data processing device, which can be implemented in software and / or hardware and integrated into an electronic device with sufficient data processing capabilities. Such electronic devices may include, but are not limited to, laptop computers, desktop computers, personal workstations, servers, and supercomputers.

[0051] Figure 3 FIG. 1 shows a flow chart of a data processing method provided by an embodiment of the present disclosure. Figure 3 As shown, the data processing method may include the following steps:

[0052] S310: Receive a data adjustment request including a target data identifier and a target adjustment value.

[0053] The target data identifier is the identifying information of the managed data to be adjusted, and can be, for example, a globally unique code. Data adjustment here refers to reducing or increasing the data holdings (also known as data values) of the managed data as needed. The managed data can be of various types, such as financial data. Specifically, the managed data can be budget data in the financial sector. A corresponding data adjustment that reduces the data value can be, for example, a deduction resulting from the acquisition of physical or virtual items, while a corresponding data adjustment that increases the data value can be, for example, a refund resulting from the return of an item. For example, the target data identifier can be obtained by encoding a combination of information consisting of the data type, data creation date, and data adjustment mode. If the system is deployed in a distributed architecture, the target data identifier can be obtained by superimposing the corresponding data sharding position information (e.g., 10 random sharding bits) on top of the above three pieces of information. Furthermore, if data adjustments are divided into main data adjustments and sub-data adjustments, the data identifier of the sub-data adjustment can be obtained by encoding a combination of information consisting of the main data adjustment's data identifier, period type, period value, sub-data adjustment's data type, and sequence number. The above data types can be categorized by the data adjustment execution method, such as periodically adjusted data and two-stage adjusted data; they can also be categorized by data usage, such as capital data, R&D data, and operational data; and they can also be categorized by flexibility, such as fixed data, elastic data, and incremental data. The above data adjustment modes are described below. The target adjustment value is the amount of data to be changed (increased or decreased) in this data adjustment.

[0054] Specifically, the user client can generate a data adjustment request in response to a user operation and send it to the electronic device integrated with the data processing service. Alternatively, the upstream business generates a data adjustment request after performing certain processing and sends it to the electronic device. The electronic device receives the data adjustment request and parses it to obtain a target data identifier and a target adjustment value.

[0055] S320, from a plurality of data adjustment modes, determine a target adjustment mode that adapts to the target data identifier; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed in a near-end, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on a memory database and a first relational database.

[0056] The data adjustment mode is a specific data adjustment logic defined in advance and executed based on a specific database. The target adjustment mode is a data adjustment mode suitable for the target data identifier. The memory database is a database management system that mainly stores data in memory, which can achieve high-speed read and write by directly operating memory. Atomic adjustment refers to integrating one or more steps related to data adjustment into an indivisible operation unit. The relational database is a database based on the relational model (such as table structure), which manages data through structured query language, has atomicity, consistency, isolation, and data persistence on disk, and supports complex queries and transaction processing. The first relational database is a relational database oriented to user clients. Transaction adjustment refers to integrating one or more steps related to data adjustment into a transaction for execution.

[0057] Specifically, the data processing scheme in the related art can only have good adaptability to a certain characteristic business scenario. This leads to poor processing effect of the original data processing scheme after switching the business scenario. Therefore, three data adjustment modes are provided in the embodiments of the present disclosure to adapt to different data adjustment business scenarios with different processing demands. Moreover, the electronic device can automatically determine the target adjustment mode that is more suitable for the current situation from the three data adjustment modes after receiving the data adjustment request.

[0058] The first data adjustment mode provided in the embodiments of the present disclosure is an atomic adjustment mode based on a memory database deployed in a near-end. As shown in FIG. 2, the atomic adjustment mode includes a data adjustment request receiving unit 201, a data adjustment mode determining unit 202, a target adjustment value determining unit 203, and a data adjustment executing unit 204. Figure 2As shown, the atomic adjustment mode deploys the atomic adjustment logic based on the memory database in the local space of the electronic device. In this way, for high-traffic business scenarios, the electronic device can call the atomic adjustment service through local access without having to perform remote calls, saving the time of remote calls and improving data adjustment efficiency. In addition, the local call data adjustment service method can greatly reduce the request traffic of the data center server and reduce its linear capacity expansion demand as the traffic grows, thereby reducing resource consumption costs and operation and maintenance costs. The general implementation process of the atomic adjustment mode is: each data identifier, its corresponding configuration data and the corresponding remaining data value are stored in the memory database, and the atomic operations in the memory database are used to execute specific data adjustment logic and data query logic (which may rely on encapsulated scripts with corresponding functions). The configuration data corresponding to the target data identifier here refers to the data value configured during the data creation and / or data increment processing of the data to be managed. For example, it can be the initially set data value (which can be called the target data value in the data creation process) or the data value reset by the later increment.

[0059] The second data adjustment mode provided by the embodiment of the present disclosure is a transaction adjustment mode based on the first relational database. Figure 2 As shown, the transaction adjustment mode is deployed on the remote server, which uses the first relational database to store each data identifier, its corresponding configuration data, its corresponding remaining data value, the flow data of the data processing process, etc. in real time. In this way, the transaction characteristics of the first relational database can be used to execute the data adjustment logic and record the operation flow data to ensure the integrity and consistency of data-related data, improve the reliability and compliance of the relevant information of the data to be managed, thereby improving the accuracy of property resource management and providing a data basis for problem troubleshooting and accurate data rollback. At the same time, after the data adjustment is completed, the first relational database can synchronize its updated remaining data values ​​to the in-memory database so that it can respond to data query requests with high concurrency and execute data query logic, while reducing the access pressure of the first relational database and improving its data adjustment processing performance to a certain extent.

[0060] The third data adjustment mode provided by the embodiment of the present disclosure is a distributed adjustment mode based on the collaboration between the memory database and the first relational database. Figure 2As shown, the distributed adjustment mode is deployed on a remote server, which records operation log data in real time through transactions of the first relational database, and stores each data identifier, its corresponding configuration data, and its corresponding residual data value, etc. in real time through an in-memory database. In this way, the transaction characteristics of the first relational database can be used to record operation log data to provide a data basis for accurate data rollback. At the same time, the in-memory database can be used to execute data adjustment logic and data query logic with high concurrency and high performance. In this way, the demands for high concurrency and high performance in data processing and the demand for data reliability in data processing can be balanced.

[0061] After the electronic device determines the target data identifier, it can determine the target adjustment mode from the three data adjustment modes according to a decision strategy of the pre-determined data adjustment mode.

[0062] In some embodiments, the decision strategy of the adjustment mode is to determine the target adjustment mode according to a pre-established mapping relationship between data identifiers and adjustment modes, that is, S320 includes: determining the target adjustment mode based on the target data identifier and the mode mapping relationship.

[0063] The mode mapping relationship records an initial data identifier and a data adjustment mode corresponding to the data adjustment scene adapted to the initial data identifier. The initial data identifier is a concept corresponding to the target data identifier, which represents the identification information of any created data. The data adjustment scene is a business scene related to data adjustment business in a data business scene, for example, it can be a high-flow high-speed data adjustment scene that pays more attention to high flow and high data processing speed, but has lower requirements for data consistency, or it can be a high-consistency data adjustment scene that pays more attention to high data consistency, but has lower requirements for data processing speed, or it can be a high-performance data adjustment scene that has a relatively balanced demand for concurrent processing capacity, data processing speed and data consistency, etc.

[0064] Specifically, in this embodiment, the processing requirements of various data adjustment scenarios and the processing effects of data adjustment modes can be analyzed and adapted in advance, and a correspondence between data adjustment scenarios and data adjustment modes can be established. For example, according to the above analysis, the atomic adjustment mode based on the memory database deployed at the near end is more suitable for processing data adjustment tasks with high traffic and relatively low data consistency, so a correspondence between the atomic adjustment mode and the above-mentioned high-traffic and high-speed data adjustment scenario can be established; the transaction adjustment mode based on the first relational database is more suitable for processing data adjustment tasks with high data consistency and relatively low speed, so a correspondence between the transaction adjustment mode and the above-mentioned high-consistency data adjustment scenario can be established; the distributed adjustment mode based on the collaboration of the memory database and the first relational database is more suitable for processing high-performance data adjustment tasks with relatively balanced concurrency, processing speed and data consistency, so a correspondence between the distributed adjustment mode and the above-mentioned high-performance data adjustment scenario can be established.

[0065] Based on the above, during the data creation process, the manager can select the appropriate data adjustment scenario for the data based on the processing requirements of the corresponding data adjustment business. After generating the initial data identifier for the created data according to the aforementioned rules, a correspondence between the initial data identifier and the data adjustment scenario can be established. By combining this correspondence between the initial data identifier and the data adjustment scenario with the aforementioned correspondence between the data adjustment scenario and the data adjustment pattern, we can obtain a correspondence between the initial data identifier, the data adjustment scenario, and the data adjustment pattern, thus generating a pattern mapping relationship.

[0066] In specific implementations, the electronic device can use the target data identifier as an index query mode mapping relationship to determine the initial data identifier that matches it. The data adjustment mode corresponding to the successfully matched initial data identifier is then determined as the target adjustment mode. This allows the target data identifier to determine a target adjustment mode that is more suitable for its data processing requirements, thereby improving the processing efficiency and accuracy of subsequent data adjustments.

[0067] In other embodiments, the decision strategy for the adjustment mode is to determine the target adjustment mode based on the execution priority of the pre-established adjustment mode, that is, S320 includes: determining the target adjustment mode from each data adjustment mode based on the priority of the data adjustment mode, the level selection condition corresponding to the priority and the current system status value.

[0068] Among them, the level selection condition is the trigger condition corresponding to each priority, which can be a condition for characterizing the current system state. Exemplarily, the level selection condition can be the size relationship between the current system state value of the first relational database and the preset system state critical value (i.e., the preset state threshold). For example, the level selection condition can be the size relationship between the current processing performance value of the first relational database and the preset performance critical value (i.e., the preset performance threshold). The above-mentioned current system state value refers to the state value of the data processing system at the current moment on the state characterization dimension corresponding to the level selection condition, for example, it can be the processing performance value of the first relational database at the current moment (i.e., the current processing performance value).

[0069] Specifically, in this embodiment, the priority and level selection conditions for triggering the priority can be set in advance for each data adjustment mode. For example, the atomic adjustment mode based on the memory database deployed at the near end is set to the lowest priority as a fallback, and its corresponding level selection condition is that there is no relational database, that is, the current system state value (such as the current processing performance value) of the first relational database is empty or a preset error value. This ensures that data adjustment can be executed and has high concurrency and high traffic processing characteristics, thereby improving the processing efficiency of data adjustment. For another example, the transaction adjustment mode based on the first relational database is set to the highest priority, and its corresponding level selection condition is that the current system state value (such as the current processing performance value) of the first relational database is less than or equal to the preset state threshold (preset performance threshold). In this way, the relational database can be given priority for data adjustment processing to ensure the integrity and consistency of the information related to the data to be managed as much as possible. For another example, the distributed adjustment mode based on the collaboration of the memory database and the first relational database is set to an intermediate priority, and its corresponding level selection condition is that the current system state value (such as the current processing performance value) of the first relational database exceeds the preset state threshold (preset performance threshold) and presents insufficient performance. This allows for more balanced concurrent processing volume and data consistency to handle data adjustments, ensuring data processing efficiency and consistency of data-related data to a certain extent.

[0070] During specific implementation, after the electronic device obtains the target data identifier, it can obtain the current system state value of the first relational database involved in the level selection condition, and process the current system state value according to the level selection condition corresponding to each priority (such as comparing it with the preset state critical value) to determine the level selection condition satisfied by the current system state value. Then, the data adjustment mode corresponding to the priority matching the satisfied level selection condition is determined as the target adjustment mode. In this way, an adjustment mode that is more suitable for the processing capacity of the current data processing system can be determined according to the system state value, thereby performing data adjustment processing more efficiently and improving adjustment efficiency.

[0071] In some other embodiments, the decision strategy for the adjustment mode is random selection. If the target data identifier or its corresponding data adjustment mode is not recorded in the mode mapping relationship, the electronic device cannot determine the target adjustment mode through the mode mapping relationship. Alternatively, if the current system state value obtained by the electronic device does not match the level selection condition of any priority, the electronic device cannot determine the target adjustment mode based on the priority. In this case, the electronic device can randomly select a data adjustment mode from the three data adjustment modes as the target adjustment mode to ensure that the data adjustment request can be processed rather than discarded.

[0072] S330 : Based on the target data identifier and the target adjustment value, execute data adjustment processing corresponding to the target adjustment mode to generate a data adjustment result.

[0073] Specifically, the electronic device locates the specific data to be managed based on the target data identifier, then performs data adjustment processing using the target adjustment value according to the data adjustment logic corresponding to the target adjustment mode. After the processing is completed, the electronic device obtains the remaining data value and a message indicating that the data adjustment was successful as the data adjustment result. If the target adjustment mode involves the first relational database, the data adjustment result may also include operation flow data.

[0074] The data processing method provided by the above-mentioned embodiments of the present disclosure is capable of receiving a data adjustment request including a target data identifier and a target adjustment value; determining a target adjustment mode that is adapted to the target data identifier from among an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, and a distributed adjustment mode based on collaboration between the memory database and the first relational database; executing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result; and realizing automatic decision-making on a more suitable data adjustment mode based on the target data identifier, so that the system's adjustment service can be more flexibly applied to various data scenarios, thereby improving the accuracy and efficiency of data adjustment in corresponding business scenarios and enhancing the system's financial resource management capabilities.

[0075] In some embodiments, if the target adjustment mode is an atomic adjustment mode or a distributed adjustment mode, first configuration data and second configuration data are obtained, and when the first configuration data is different from the second configuration data, the configuration data corresponding to the target data identifier in the fourth data table stored in the memory database is updated based on the second configuration data.

[0076] Among them, the first configuration data is the configuration data corresponding to the latest target data identifier recorded in the memory database before the configuration data update is executed. The second configuration data is the configuration data corresponding to the target data identifier most recently recorded in the relational database corresponding to the business party / data management party (referred to as the second relational database). The memory database in this embodiment can be a memory database corresponding to the atomic adjustment mode or a memory database corresponding to the distributed adjustment mode. Correspondingly, the fourth data table is a data table corresponding to the atomic adjustment mode (referred to as the first data table) or a data table corresponding to the distributed adjustment mode (referred to as the third data table).

[0077] Specifically, see Figure 4 , the configuration data corresponding to the target data identifier in the embodiment of the present disclosure is managed by the management client through the second relational database in the data management system to perform operations such as data creation / data increment. For the atomic adjustment mode based on the memory database deployed at the near end or the distributed adjustment mode in collaboration with the first relational database, the configuration data corresponding to the target data identifier needs to be synchronized from the second relational database to the memory database. The data synchronization process can adopt the data synchronization algorithm in the relevant technology. In order to save resource consumption, in this embodiment, data synchronization is performed when the user client actively initiates a request. For example, after the user client initiates a data adjustment request, any server corresponding to the electronic device can trigger the execution of the data synchronization process in response to the request. For another example, the user client monitors the timer. After the timer arrives and the first data adjustment request is received, any server can also trigger the execution of the data synchronization process in response to the request. In this way, the processing process of the data adjustment request can be merged with the synchronization process of the configuration data corresponding to the target data identifier of the databases at both ends, instead of using complex data synchronization logic.

[0078] The specific data synchronization process may be as follows: the server pulls the second configuration data from the second relational database and the first configuration data from its corresponding in-memory database. The server then compares the first and second configuration data. If they are identical, the data are synchronized, and the synchronization process ends. If they are different, the second configuration data is used to update the configuration data corresponding to the target data identifier in the in-memory database, thereby updating the first configuration data, thus achieving synchronization of the configuration data corresponding to the target data identifier in the in-memory database.

[0079] It should be noted that the above data synchronization process is applicable at least after the first configuration data synchronization. That is, the synchronization of the first configuration data is achieved by the synchronization method in the subsequent data creation related embodiments, and the subsequent data synchronization process can be achieved by referring to the above embodiments.

[0080] Figure 5A flow chart of another data processing method provided by an embodiment of the present disclosure is shown. This data processing method further refines the steps of "based on the target data identifier and the target adjustment value, executing the data adjustment processing corresponding to the target adjustment mode and generating a data adjustment result" in each data adjustment mode to implement the corresponding data adjustment process, thereby improving the accuracy of data adjustment and enhancing the integrity and consistency of data-related data and pipeline data.

[0081] like Figure 5 As shown, the data processing method may include the following steps:

[0082] S501: Receive a data adjustment request including a target data identifier and a target adjustment value.

[0083] S502: Determine a target adjustment mode that is adapted to the target data identifier from multiple data adjustment modes.

[0084] S503. If the target adjustment mode is the atomic adjustment mode, then in the atomic operation based on the local memory database, the first initial data value in the first data table is determined based on the target data identifier, and based on the first initial data value and the target adjustment value, data adjustment processing is performed to generate a data adjustment result, and the first data table is updated based on the data adjustment result.

[0085] Among them, the first data table is a data table corresponding to the atomic adjustment mode based on the memory database deployed at the near end, which records the relevant information of the specific data to be managed (such as the initial data identifier, the initial data value, the data adjustment amount, the remaining data value after the data adjustment, the processing status of the data adjustment request, etc.). In order to achieve accurate data rollback processing, the first data table can be made idempotent in the embodiment of the present disclosure. The specific implementation method of this idempotence is not limited. For example, for the atomic adjustment mode based on the memory database, the idempotence of the first data table can be controlled by implementing unique key constraints or transactions by developing scripts and the like. The first initial data value is the data value recorded in the first data table before this data adjustment processing.

[0086] Specifically, for scenarios with high traffic, high concurrency, and weak data consistency requirements, the target adjustment mode can be an atomic adjustment mode based on a memory database deployed proximally. The data adjustment process is as follows: after verifying the legitimacy of the data adjustment request, the electronic device calls the adjustment service in the atomic operation of the local memory database. The adjustment service first determines the first initial data value corresponding to this data adjustment from the first data table based on the target data identifier. Then, data adjustment processing is performed based on the first initial data value and the target adjustment value.

[0087] For data adjustment logic that reduces the amount of data, if the first initial data value is less than the target adjustment value, a message indicating that the data adjustment failed and / or the reason for the data adjustment failure are used as the data adjustment result. If the first initial data value is greater than or equal to the target adjustment value, but the data adjustment still fails, a retry mechanism can be added to retry the data adjustment until a pre-set retry end condition is met, and a message indicating that the data adjustment failed and / or the reason for the data adjustment failure are used as the data adjustment result. If the first initial data value is greater than or equal to the target adjustment value, the target adjustment value is subtracted from the first initial data value to obtain a remaining data value, which is used together with a message indicating that the adjustment was successful as the data adjustment result. For data adjustment logic that increases the amount of data, the first initial data value can be added to the target adjustment value to obtain a remaining data value after the data adjustment, which is used together with a message indicating that the adjustment was successful as the data adjustment result.

[0088] Afterwards, the electronic device may use the data adjustment result to update the relevant information of the to-be-managed data corresponding to the target data identifier in the first data table.

[0089] S504: If the target adjustment mode is the transaction adjustment mode, a first transaction is started through the first relational database, and a first shard position is determined based on the target data identifier within the first transaction.

[0090] The first shard location is the physical or logical storage location of the data shard in the first relational database that is distributedly deployed in the above-mentioned transaction adjustment mode.

[0091] Specifically, for a distributed system in a property resource management scenario, it requires strong consistency between the shard location corresponding to data management and the shard location recorded in the routing table. Therefore, when data is created, its corresponding shard location can be determined based on the data and system conditions, that is, the data identifier and the shard location have a corresponding relationship, and are stored in the global routing table. Therefore, when the electronic device determines that the target adjustment mode is a transaction adjustment mode based on a first relational database, in order to ensure data consistency and accurate rollback, it can first start a transaction (i.e., a first transaction), and then query the global routing table according to the target data identifier in the first transaction to determine the first shard location corresponding to the target data identifier. The first shard location can store the second data table corresponding to the target data identifier, the first operation flow table, and the adjustment logic corresponding to the transaction adjustment mode, etc.

[0092] S505: Add a first pessimistic lock to the second data table and the first operation flow table stored in the first shard position, and insert a first adjustment record into the first operation flow table.

[0093] Among them, the second data table is a data table corresponding to the transaction adjustment mode of the first relational database, which records the relevant information of the specific data to be managed. The first operation flow table is a data table corresponding to the transaction adjustment mode of the first relational database, which records the flow data of the processing operations related to the data. Similarly, in order to ensure the consistency and idempotence of the data, the second data table and the first operation flow table are made idempotent in this embodiment. This idempotence can be achieved through the transaction characteristics of the first relational database. The first adjustment record is an adjustment record recorded in the first operation flow table, which may include at least part of the contents such as the timestamp, data identifier, the initial data value before the data adjustment, the data adjustment value, the remaining data value after the data adjustment, the processing status of the data adjustment request and the data adjustment mode.

[0094] Specifically, to prevent data table write conflicts, the electronic device can, in the first transaction, add a pessimistic lock (referred to as a first pessimistic lock) to the second data table and the first operation flow table stored in the first shard location. Then, based on the target data identifier, a first adjustment record is inserted into the first operation flow table to record the flow of operations for the data adjustment request corresponding to the target data identifier being processed. Because no data adjustment has been performed at this moment, the processing status in the first adjustment record is the initial state.

[0095] S506 : Execute data adjustment processing based on the second initial data value and the target adjustment value in the second data table to generate a data adjustment result.

[0096] The second initial data value is the data value recorded in the second data table before the current data adjustment process.

[0097] Specifically, the electronic device invokes an adjustment service in a first transaction. The adjustment service first determines, from a second data table, a second initial data value corresponding to the current data based on the target data identifier. Then, based on the second initial data value and the target adjustment value, data adjustment processing is performed in accordance with the relevant descriptions in the aforementioned embodiments to generate a data adjustment result.

[0098] S507 : Based on the data adjustment result, the second data table and the first adjustment record are updated respectively, the first transaction is committed, and the first pessimistic lock is released.

[0099] Specifically, during the first transaction, the electronic device can use the data adjustment result to update the relevant information of the to-be-managed data corresponding to the target data identifier in the second data table, and update the first adjustment record based on the data adjustment result. For example, at least the remaining data value after the data adjustment operation is added, and the processing status is updated to failure or success, etc., to ensure the integrity and accuracy of the data table and operation flow.

[0100] S508: If the target adjustment mode is the distributed adjustment mode, a second transaction is started through the first relational database, and the second shard position is determined based on the target data identifier in the second transaction.

[0101] The second shard location is the physical or logical storage location of the data shard in the first relational database that is distributedly deployed in the above-mentioned distributed adjustment mode.

[0102] Specifically, when the electronic device determines that the target adjustment mode is a distributed adjustment mode based on the collaboration between the in-memory database and the first relational database, to ensure data consistency and accurate rollback, it can first start a transaction (i.e., a second transaction), and then query the global routing table based on the target data identifier in the second transaction to determine the second shard location corresponding to the target data identifier. The second shard location can store the third data table corresponding to the target data identifier, the second operation flow table, and the data adjustment logic corresponding to the distributed adjustment mode.

[0103] S509: Add a second pessimistic lock to the second operation flow table stored at the second shard position, and insert a second adjustment record into the second operation flow table.

[0104] The second operation flow table is a data table corresponding to the above-mentioned distributed adjustment mode, recording the flow data of data-related processing operations. Similarly, to ensure data consistency and idempotence, the second operation flow table is made idempotent in this embodiment. This idempotence can be achieved through the transaction characteristics of the second relational database. The second adjustment record is an adjustment record recorded in the second operation flow table, which may include at least part of the following content: a timestamp, a data identifier, the initial data value before the data adjustment, the data adjustment value, the remaining data value after the data adjustment, the processing status of the data adjustment request, and the data adjustment mode.

[0105] Specifically, to prevent data table write conflicts, the electronic device can, in the second transaction, add a pessimistic lock (referred to as a second pessimistic lock) to the second operation flow table stored at the second shard location. Then, based on the target data identifier, a second adjustment record is inserted into the second operation flow table to record the flow operation for the data adjustment request corresponding to the target data identifier being processed. Because no data adjustment has been performed at this moment, the processing status in the second adjustment record is the initial state.

[0106] S510. In an atomic operation based on an in-memory database, determine a third initial data value in a third data table based on a target data identifier, and perform data adjustment processing based on the third initial data value and a target adjustment value to generate a data adjustment result.

[0107] The third data table is a data table corresponding to the distributed adjustment mode and recording the related information of the specific to-be-managed data. Similarly, in order to ensure the consistency and idempotency of the data, the third data table is made to have idempotency in this embodiment. The idempotency can be realized by the transaction feature of the second relational database. The third initial data value is the data value recorded in the third data table before the current data adjustment processing.

[0108] Specifically, in the distributed adjustment mode, the operation stream data is stored in the first relational database to ensure the accuracy of data rollback. In order to reduce the resource consumption of the first relational database and improve the concurrency of data adjustment, the data adjustment is performed through the in-memory database in the adjustment mode. Therefore, the electronic device calls the data adjustment service based on the in-memory database in the second transaction. In the atomic operation of the in-memory database, the data adjustment service first determines the third initial data value corresponding to the current data from the third data table according to the target data identifier. Then, according to the third initial data value and the target adjustment value, the data adjustment processing is performed according to the related description in the foregoing embodiments to generate the data adjustment result.

[0109] S511, update the third data table and the second adjustment record based on the data adjustment result respectively, submit the second transaction, and release the second pessimistic lock.

[0110] Specifically, in the second transaction, the electronic device can use the data adjustment result to update the related information of the to-be-managed data corresponding to the target data identifier in the third data table, and update the second adjustment record according to the data adjustment result. For example, at least the remaining data value after the current data adjustment operation is added, and the processing state is updated to failure or success, etc., to ensure the integrity and accuracy of the data table and the operation stream.

[0111] Figure 6 A flowchart of another data processing method provided by an embodiment of the present disclosure is shown. The data processing method can be applied to various scenarios of data management through online services, and is particularly suitable for scenarios in which a management party manages data by creating, changing, etc. to address the problem of weak data management capability and inability to better ensure the consistency of created data values in related technologies when only a data value is simply configured when creating a data resource. The method can be executed by a data processing apparatus, which can be implemented in software and / or hardware, and can be integrated into an electronic device having certain data processing capability. The electronic device can include, but is not limited to, a notebook computer, a desktop computer, a personal workstation, a server, a supercomputer, etc.

[0112] As Figure 6 shown, the data processing method can include the following steps:

[0113] S610 : In response to a received data creation request including a target data value, generate an initial data identifier.

[0114] The target data value is the data value configured when creating new data to be managed. A data creation request is an access request that triggers the execution of the data creation process and may include at least the target data value and the data type. Given that various data adjustment modes exist in the disclosed embodiments to accommodate various data adjustment scenarios, a data creation request may also include a data adjustment mode or scenario. The initial data identifier is globally unique identification information generated when a data resource is created.

[0115] Specifically, the data manager can input the target data value through the human-computer interaction interface provided by the data management system, and trigger the relevant function control to initiate a data creation request for a new data resource. Alternatively, for some periodic data adjustment tasks, a timer can be set to trigger the data creation request at regular intervals. After receiving the data creation request, the electronic device can parse it to obtain the target data value and data type, and can also parse it to obtain the data adjustment mode or data adjustment scenario. Then, the electronic device can generate the initial data identifier corresponding to the data creation request in accordance with the pre-set data identifier generation rules, combined with the current system time, data type, data adjustment mode or data adjustment scenario. If the data processing system is a distributed architecture, the electronic device can generate the initial data identifier corresponding to the data creation request in combination with the current system time, data type, data adjustment mode or data adjustment scenario, and sharding position (such as 10 random sharding bits).

[0116] S620: Create configuration data corresponding to the initial data identifier in the general data table based on the target data value.

[0117] The total data table is a data table facing the management client and records relevant information of all the data to be managed.

[0118] Specifically, the electronic device may add a piece of configuration data created this time to the general data table, and the configuration data corresponding to the initial data identifier at least includes an initial data identifier, a creation timestamp, and a target data value.

[0119] In some embodiments, S620 includes: opening a third transaction through a second relational database, and inserting a data creation record in a third operation flow table based on an initial data identifier within the third transaction; when the initial data identifier and the target data value meet the idempotent condition, creating configuration data corresponding to the initial data identifier in the total data table based on the target data value, and after updating the data creation record based on the configuration data corresponding to the initial data identifier, committing the third transaction.

[0120] Among them, the second relational database is a relational database for management clients, which can store the data processing logic and related data corresponding to the management party. The third operation flow table is a data table used to record the flow data of related processing operations in the data configuration process (such as the creation process, the change process, etc.). The data creation record is a flow operation record that records the relevant information in the data creation process, which may include at least part of the timestamp, initial data identifier, target data value and the processing status of the data creation request. The idempotence condition is a pre-set condition used to determine whether the data creation request has idempotence.

[0121] Specifically, to ensure the atomicity, isolation, consistency, and durability of data creation, this embodiment executes the data creation process through transactions. To persist the operation flow data during the data creation process, this embodiment can store a third operation flow table in the second relational database. Furthermore, to enable precise rollbacks, this embodiment can implement idempotent processing on data creation requests during the data creation process.

[0122] In a specific implementation, the electronic device initiates a third transaction through the second relational database, executing the following process within the third transaction: First, a data creation record is inserted into the third operation flow table based on the initial data identifier to record the data creation operation, with the processing status set to the initial, unprocessed state. Next, an idempotency condition is determined. Specifically, using the idempotency determination rules in related technologies, a determination is made as to whether the current data creation request is idempotent based on the initial data identifier. If so, a determination is made as to whether the target data value is the same data value. If so, and the idempotency condition is determined to be met, the data creation corresponding to the initial data identifier is re-executed using the target data value. If the data creation request is not idempotent, and the idempotency condition is determined not to be met, the data creation corresponding to the initial data identifier is directly executed using the target data value. Subsequently, configuration data corresponding to the initial data identifier is created in the general data table based on the initial data identifier and the target data value, thereby completing the current data creation. Finally, the processing status in the data creation record in the third operation flow table is updated based on the configuration data corresponding to the initial data identifier, and the third transaction is committed.

[0123] S630: query the data synchronization request table corresponding to the user client based on the initial data identifier, and when it is determined through the data synchronization request table that the initial data identifier is not idempotent, determine a target adjustment mode that is adapted to the initial data identifier from multiple data adjustment modes.

[0124] The data synchronization request table records the data identifier, configuration data, and synchronization status corresponding to the synchronization request. This table is used to determine the idempotence of the synchronization request for the configuration data corresponding to the initial data identifier. Data adjustment modes include an atomic adjustment mode based on a near-end in-memory database, a transactional adjustment mode based on a second relational database, and a distributed adjustment mode based on a collaboration between the in-memory database and a second relational database.

[0125] Specifically, after the management client triggers the electronic device to create new data to be managed based on the second relational database, the configuration data for the data to be managed must be synchronized with the server corresponding to the user client so that the user client can correctly execute the data adjustment logic after triggering the data adjustment request. Therefore, the electronic device can construct a data synchronization request using the initial data identifier and the target data value. After establishing a connection with the server corresponding to the user client, the electronic device queries the data synchronization request table maintained on the server corresponding to the user client. For example, the electronic device can send a data synchronization request to the server corresponding to the user client, triggering the server to query the data synchronization request table maintained therein using the data synchronization request. For another example, the electronic device can retrieve the data synchronization request table from the server corresponding to the user client and query it locally. When querying the data synchronization request table, the electronic device determines whether the data synchronization request corresponding to the initial data identifier and the target data value is idempotent. If it is idempotent, the configuration data corresponding to the initial data identifier has been correctly synchronized to the server, and there is no need to repeat the synchronization operation, ending the current process. If it is not idempotent, synchronization of the configuration data corresponding to the initial data identifier must be performed.

[0126] During synchronization of the configuration data corresponding to the initial data identifier, given that different data adjustment modes correspond to different databases, the electronic device can first determine the target adjustment mode corresponding to the initial data identifier before determining the database to be synchronized. Furthermore, the electronic device can synchronize the configuration data corresponding to the initial data identifier according to the data synchronization method of the corresponding database. Therefore, the electronic device can refer to S320 and the description of related embodiments to determine the target adjustment mode that matches the initial data identifier from multiple data adjustment modes.

[0127] In some embodiments, before determining the target adjustment mode in S630, the method further includes: if it is determined that the initial data identifier corresponds to periodic adjustment data, generating a periodic adjustment data slice; in the periodic adjustment data slice, triggering the step of determining a target adjustment mode adapted to the initial data identifier from multiple data adjustment modes in S630.

[0128] Periodically adjusted data is a data type that divides the data adjustment period into specific time intervals or business cycles, and then compiles, monitors, and evaluates data for each time period or business cycle. Periodically adjusted data shards are used to manage / process data within a data adjustment period.

[0129] Specifically, after determining that the data synchronization request is not idempotent, the electronic device may first determine whether the data type corresponding to the initial data identifier is periodic adjustment data. If not, the electronic device may continue to perform the aforementioned step of determining a target adjustment mode that is adapted to the initial data identifier from multiple data adjustment modes. If so, the electronic device may first generate a periodic adjustment data slice based on the initial data identifier and the target data value, and then perform the step of determining a target adjustment mode that is adapted to the initial data identifier from multiple data adjustment modes in S630 and subsequent steps within the periodic adjustment data slice.

[0130] It should be noted that if the data is periodically adjusted, then the division method of periodically adjusted data in related technologies can be used to generate sub-data identifiers and their corresponding data values, etc.

[0131] S640: Update the target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier.

[0132] The target data table is the data table corresponding to the target adjustment mode. For example, if the target adjustment mode is the atomic adjustment mode based on an in-memory database deployed locally, the target data table is the first data table in the in-memory database; if the target adjustment mode is the transactional adjustment mode based on a first relational database, the target data table is the second data table in the first relational database; if the target adjustment mode is the distributed adjustment mode based on the collaboration between the in-memory database and the first relational database, the target data table is the third data table in the in-memory database.

[0133] Specifically, the electronic device uses information such as the initial data identifier, the configuration data corresponding to the target data identifier, and the target adjustment mode to construct a data synchronization request, and sends it to the server corresponding to the user client to trigger the server to perform data synchronization. In response to the data synchronization request, the server uses the target adjustment mode to determine the target data table in the corresponding database; then uses the initial data identifier to locate the corresponding record from the target data table, and uses the configuration data corresponding to the initial data identifier to update the corresponding record in the target data table, completing the update of the configuration data corresponding to the initial data identifier. Finally, the electronic device can update the aforementioned data synchronization request table corresponding to the initial data identifier based on the update result of the configuration data corresponding to the initial data identifier fed back by the server (such as the update timestamp, the processing status of the update success or failure, etc.) to complete the relevant records of this data update.

[0134] It should be noted that in order to further ensure data consistency and rollback accuracy, idempotency processing of the corresponding idempotent table can be performed before and after the target data table is updated.

[0135] In some embodiments, S640 includes: opening a fourth transaction through the second relational database, within the fourth transaction, using the initial data identifier and the configuration data corresponding to the initial data identifier to update the target data table corresponding to the target adjustment mode, and after updating the data synchronization request table, committing the fourth transaction.

[0136] Specifically, to ensure consistency in updating the configuration data corresponding to the initial data identifier, the data update process can be performed via a transaction. Thus, the electronic device can initiate a fourth transaction via the second relational database and perform the data update process within the fourth transaction. Then, after updating the data synchronization request table, the fourth transaction is submitted.

[0137] The data processing method provided by the above-mentioned embodiments of the present disclosure can generate an initial data identifier in response to a received data creation request including a target data value; create configuration data corresponding to the initial data identifier in a general data table based on the target data value; query the data synchronization request table corresponding to the user client based on the initial data identifier, and when it is determined through the data synchronization request table that the initial data identifier is not idempotent, determine a target adjustment mode adapted to the initial data identifier from multiple data adjustment modes; wherein the data synchronization request table is used to record the data identifier, configuration data and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed at the near end, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on the collaboration between the memory database and the second relational database; update the target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier; realize data creation, and perform data synchronization based on data consistency for data tables corresponding to different data adjustment modes during the data creation process, thereby improving the efficiency and accuracy of data creation, providing a good data foundation for accurate data adjustment in different subsequent business scenarios, and further improving the financial resource management capabilities of the system.

[0138] Figure 7 A schematic diagram of the process flow for incremental data processing in a data processing method provided by an embodiment of the present disclosure is shown. This data processing method can perform incremental change processing on already created data and, during the data change process, synchronize data tables corresponding to different data adjustment modes based on data consistency, further improving the efficiency and accuracy of data management. This provides a good data foundation for accurate data adjustments in subsequent different business scenarios, thereby further enhancing the system's financial resource management capabilities.

[0139] like Figure 7 As shown, the data increment processing process in the data processing method may include the following steps:

[0140] S710: Receive a data increment request including an initial data identifier and a target increment value.

[0141] The target increment value is the amount of data to be added to the already created data to be managed initiated by the management party. The data increment request is a request to trigger the execution of data increment processing.

[0142] Specifically, the data manager can trigger the data increment function through the human-computer interaction interface provided by the data management system and enter the target increment value to generate a data increment request. Alternatively, for some periodic data adjustment tasks, a timer can be set to periodically trigger the data increment request. After receiving the data increment request, the electronic device can parse it to obtain the initial data identifier and the target increment value.

[0143] S720: Start a fifth transaction through the second relational database, and insert a data increment record into the third operation flow table based on the initial data identifier within the fifth transaction.

[0144] Among them, the data increment record is a pipeline operation record that records relevant information in the data increment process, which may include at least part of the timestamp, initial data identifier, target data value, target increment value and processing status of the data increment request.

[0145] Specifically, the electronic device starts a fifth transaction through the second relational database to perform data increment processing of the configuration data corresponding to the initial data identifier in the total data table in the fifth transaction to improve data consistency.

[0146] During specific implementation, in the fifth transaction, the electronic device first inserts a new data increment record into the third operation flow table according to the initial data identifier to record this data increment operation, and the processing state thereof is the initial unprocessed state.

[0147] S730. When the initial data identifier and the target incremental value meet the idempotent condition, the configuration data corresponding to the initial data identifier in the total data table is updated using the target incremental value, and after the data incremental record is updated based on the configuration data corresponding to the updated initial data identifier, the fifth transaction is committed.

[0148] Specifically, the electronic device judges the idempotency condition of the data delta request. That is, according to the rule of idempotency judgment in the related art, it is judged whether the data delta request is idempotent according to the initial data identifier. If it is idempotent, it is further judged whether the target delta value is also the same data value. If yes, it is determined that the idempotency condition is met, and then the data delta corresponding to the initial data identifier is executed again using the target delta value. If the data delta request is not idempotent, it is determined that the idempotency condition is not met, and then the data delta corresponding to the initial data identifier can be directly executed using the target delta value. Then, the electronic device can add a pessimistic lock (which can be referred to as a third pessimistic lock) to at least one row of records corresponding to the initial data identifier in the total data table to prevent other tasks from writing to the row of data. At this time, the electronic device can locate the corresponding configuration data from the total data table according to the initial data identifier, and then superimpose the target delta value on the basis of the target data value to obtain a new total data value corresponding to the initial data identifier, and update the target data value corresponding to the configuration data corresponding to the corresponding initial data identifier. Then, the electronic device can update the data delta record, such as updating at least the processing state to success or failure, and then committing the fifth transaction.

[0149] S740, query the data synchronization request table based on the initial data identifier, and determine the target adjustment mode from each data adjustment mode when it is determined that the initial data identifier is not idempotent in the data synchronization request table.

[0150] This step can refer to the related description of S630.

[0151] S750, start a sixth transaction through the second relational database, and update the target data table using the initial data identifier and the target delta value in the sixth transaction, and commit the sixth transaction.

[0152] This step can refer to the related description of S640, except that the updated data is the target delta value corresponding to the initial data identifier or the updated configuration data corresponding to the initial data identifier.

[0153] It should be noted that if the third pessimistic lock is added to some data in the total data table in the foregoing steps, the third pessimistic lock can be released after the sixth transaction is committed, so as to ensure that the updated configuration data corresponding to the initial data identifier in the total data table remains unchanged during the entire data delta process, thereby ensuring the accuracy of data synchronization.

[0154] The following is an embodiment of a data processing apparatus provided by the embodiment of the present disclosure. The apparatus and the data processing method of each embodiment described above belong to the same inventive concept. Details not described in detail in the embodiment of the data processing apparatus can be referred to the embodiment of the data processing method.

[0155] Figure 8FIG. 1 shows a schematic diagram of the structure of a data processing device provided by an embodiment of the present disclosure. Figure 8 As shown, the data processing device 800 may include:

[0156] The request receiving module 810 is configured to receive a data adjustment request, wherein the data adjustment request includes a target data identifier and a target adjustment value;

[0157] A first adjustment mode determination module 820 is configured to determine a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes; wherein the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on a collaboration between the memory database and the first relational database;

[0158] The data adjustment module 830 is configured to execute data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value, and generate a data adjustment result.

[0159] The data processing device provided by the above-mentioned embodiments of the present disclosure is capable of receiving a data adjustment request including a target data identifier and a target adjustment value; determining a target adjustment mode that is adapted to the target data identifier from the atomic adjustment mode based on the memory database deployed proximally, the transaction adjustment mode based on the first relational database, and the distributed adjustment mode based on the collaboration between the memory database and the first relational database; executing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result; and realizing automatic decision-making of a more suitable data adjustment mode based on the target data identifier, so that the system's data adjustment service can be more flexibly applied to various data adjustment scenarios, thereby improving the accuracy and efficiency of data adjustment in corresponding business scenarios and enhancing the system's data management capabilities.

[0160] In some embodiments, the first adjustment mode determination module 820 is specifically configured to:

[0161] The target adjustment mode is determined based on the query mode mapping relationship of the target data identifier; wherein the mode mapping relationship records the initial data identifier and the data adjustment mode adapted to the data adjustment scenario corresponding to the initial data identifier.

[0162] In some other embodiments, the first adjustment mode determining module 820 is specifically configured to:

[0163] A target adjustment mode is determined from the data adjustment modes based on the priorities of the data adjustment modes, the level selection conditions corresponding to the priorities, and the current system state value.

[0164] In some embodiments, the data adjustment mode 830 is specifically used to:

[0165] If the target adjustment mode is the atomic adjustment mode, then in the atomic operation based on the local memory database, the first initial data value in the first data table is determined based on the target data identifier, and based on the first initial data value and the target adjustment value, data adjustment processing is performed to generate a data adjustment result, and the first data table is updated based on the data adjustment result; wherein, the first data table has idempotence.

[0166] In some other embodiments, the data adjustment module 830 is specifically configured to:

[0167] If the target adjustment mode is the transaction adjustment mode, a first transaction is started through the first relational database, and a first shard position is determined based on the target data identifier within the first transaction;

[0168] Add a first pessimistic lock to the second data table and the first operation flow table stored in the first shard location, and insert a first adjustment record into the first operation flow table; wherein the second data table and the first operation flow table have idempotence;

[0169] Based on the second initial data value and the target adjustment value in the second data table, performing data adjustment processing to generate a data adjustment result;

[0170] The second data table and the first adjustment record are updated respectively based on the data adjustment result, the first transaction is committed, and the first pessimistic lock is released.

[0171] In some further embodiments, the data adjustment module 830 is specifically configured to:

[0172] If the target adjustment mode is the distributed adjustment mode, a second transaction is started through the first relational database, and a second shard position is determined based on the target data identifier within the second transaction;

[0173] Add a second pessimistic lock to the second operation flow table stored in the second shard location, and insert a second adjustment record into the second operation flow table; wherein the second operation flow table has idempotence;

[0174] In an atomic operation based on an in-memory database, a third initial data value in a third data table is determined based on the target data identifier, and data adjustment processing is performed based on the third initial data value and the target adjustment value to generate a data adjustment result; wherein the third data table has idempotence;

[0175] Based on the data adjustment result, the third data table and the second adjustment record are updated respectively, the second transaction is committed, and the second pessimistic lock is released.

[0176] In some embodiments, the data processing device 800 further includes a data updating module configured to:

[0177] If the target adjustment mode is the atomic adjustment mode or the distributed adjustment mode, the first configuration data and the second configuration data are obtained, and when the first configuration data is different from the second configuration data, the configuration data corresponding to the target data identifier in the fourth data table stored in the in-memory database is updated based on the second configuration data; wherein, the second configuration data is the configuration data corresponding to the target data identifier last recorded in the second relational database corresponding to the business party, and the first configuration data is the configuration data corresponding to the target data identifier recorded before the configuration data update is executed in the in-memory database; the fourth data table is the first data table corresponding to the atomic adjustment mode or the third data table corresponding to the distributed adjustment mode.

[0178] Figure 9 FIG. 1 shows a schematic diagram of the structure of another data processing device provided by an embodiment of the present disclosure. Figure 9 As shown, the data processing device 900 may include:

[0179] The initial data identifier generating module 910 is configured to generate an initial data identifier in response to a received data creation request, wherein the data creation request includes a target data value;

[0180] A configuration data creation module 920 is configured to create configuration data corresponding to the initial data identifier in the general data table based on the target data value;

[0181] A second adjustment mode determination module 930 is configured to query a data synchronization request table corresponding to the user client based on the initial data identifier, and when determining through the data synchronization request table that the initial data identifier is not idempotent, determine a target adjustment mode that is adapted to the initial data identifier from multiple data adjustment modes; wherein the data synchronization request table is configured to record the data identifier, configuration data, and synchronization status corresponding to the synchronization request; and data adjustment modes include an atomic adjustment mode based on a near-end in-memory database, a transactional adjustment mode based on a second relational database, or a distributed adjustment mode based on collaboration between the in-memory database and the second relational database.

[0182] The target data table updating module 940 is configured to update the target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier.

[0183] The data processing apparatus provided by the above embodiments of the present disclosure can generate an initial data identifier in response to a received data creation request including a target data value, create configuration data corresponding to the initial data identifier in a total data table based on the target data value, query a data synchronization request table corresponding to a user client based on the initial data identifier, and determine a target adjustment mode that adapts to the initial data identifier from a plurality of data adjustment modes when it is determined that the initial data identifier is not idempotent through the data synchronization request table. The data synchronization request table is used to record data identifiers, configuration data, and synchronization states corresponding to synchronization requests. The data adjustment modes include an atomic adjustment mode based on an in-memory database deployed in a near-end, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on cooperation between the in-memory database and the second relational database. The target data table corresponding to the target adjustment mode is updated by using the initial data identifier and the configuration data corresponding to the initial data identifier. The creation of the data to be managed is implemented, and the data synchronization based on data consistency is performed on the data tables corresponding to different data adjustment modes in the data creation process, which improves the efficiency and accuracy of data creation, provides a good data basis for accurate data adjustment in subsequent different business scenarios, and further improves the data management capability of the system.

[0184] In some embodiments, the configuration data creation module 920 is specifically configured to:

[0185] The third transaction is started through the second relational database, and a data creation record is inserted in the third operation flow table based on the initial data identifier in the third transaction;

[0186] When the initial data identifier and the target data value satisfy the idempotent condition, the configuration data corresponding to the initial data identifier is created in the total data table based on the target data value, and after the data creation record is updated based on the configuration data corresponding to the initial data identifier, the third transaction is committed.

[0187] In some embodiments, the target data table update module 940 is specifically configured to:

[0188] The fourth transaction is started through the second relational database, and the target data table corresponding to the target adjustment mode is updated by using the initial data identifier and the configuration data corresponding to the initial data identifier in the fourth transaction, and the fourth transaction is committed after the data synchronization request table is updated.

[0189] In some embodiments, the second adjustment mode determination module 930 is further configured to:

[0190] Before determining the target adjustment mode that adapts to the initial data identifier from the plurality of data adjustment modes, if it is determined that the initial data identifier corresponds to periodic adjustment data, the periodic adjustment data shard is generated;

[0191] In the periodic adjustment of data fragmentation, a step of determining a target adjustment mode adapted to the initial data identifier from a plurality of data adjustment modes is triggered.

[0192] In some embodiments, the data processing device 900 further includes a data increment module for:

[0193] Receive a data increment request; wherein the data increment request includes an initial data identifier and a target increment value;

[0194] Opening a fifth transaction through the second relational database, and inserting a data increment record into the third operation flow table based on the initial data identifier within the fifth transaction;

[0195] When the initial data identifier and the target incremental value meet the idempotent condition, the configuration data corresponding to the initial data identifier in the total data table is updated using the target incremental value, and after the data incremental record is updated based on the configuration data corresponding to the updated initial data identifier, the fifth transaction is committed;

[0196] Query the data synchronization request table based on the initial data identifier, and when it is determined through the data synchronization request table that the initial data identifier is not idempotent, determine the target adjustment mode from various data adjustment modes;

[0197] A sixth transaction is started through the second relational database. Within the sixth transaction, the target data table is updated using the initial data identifier and the target incremental value, and the sixth transaction is committed.

[0198] The data processing device provided by the embodiments of the present disclosure can execute the data processing method provided by any embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0199] It is worth noting that in the embodiment of the above-mentioned data processing device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this disclosure.

[0200] The present disclosure also provides an electronic device that may include a processor and a memory, wherein the memory may be used to store executable instructions. The processor may be used to read the executable instructions from the memory and execute the executable instructions to implement the data processing method in the above embodiment.

[0201] Figure 10 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown.

[0202] like Figure 10As shown, the electronic device 1000 may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. Various programs and data required for the operation of the electronic device 1000 are also stored in the RAM 1003. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output interface (I / O interface) 1005 is also connected to the bus 1004.

[0203] Typically, the following devices may be connected to the I / O interface 1005: an input device 1006 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1008 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data.

[0204] It should be noted that Figure 10 The electronic device 1000 shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure. Figure 10 The electronic device 1000 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0205] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the network isolation policy management method of any embodiment of the present disclosure are performed.

[0206] An embodiment of the present disclosure further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the network isolation policy management method in any embodiment of the present disclosure.

[0207] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. For example, a computer-readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0208] In some embodiments, the client and server can communicate using any currently known or future developed network protocol, such as the Hypertext Transfer Protocol (HTTP), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), internets (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

[0209] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0210] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the network isolation policy management method described in any embodiment of the present disclosure.

[0211] In embodiments of the present disclosure, computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0212] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the devices, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0213] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Parts (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), and the like.

[0214] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0215] Moreover, while operations are depicted in a particular order, this should not be understood as requiring such an order nor infringing on the scope of the disclosure. Certain of the operations described in the discussion are combinable into a single operation, and certain operations can be separated into several operations. In some embodiments, the operations described in the discussion can be performed in an order different than presented in the discussion. In some embodiments, the operations described in the discussion can be performed concurrently. Also, while several specific implementation details are discussed in the discussion, these should not be interpreted as limiting the scope of the disclosure. Rather, certain features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0216] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A data processing method, characterized in that: include: receiving a data adjustment request; wherein the data adjustment request includes a target data identifier and a target adjustment value; Determining a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes; wherein the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on collaboration between the memory database and the first relational database; Based on the target data identifier and the target adjustment value, a data adjustment process corresponding to the target adjustment mode is performed to generate a data adjustment result.

2. The method according to claim 1, characterized in that The step of determining a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes includes: The target adjustment mode is determined based on the target data identifier query mode mapping relationship; wherein the mode mapping relationship records the initial data identifier and the data adjustment mode adapted to the data adjustment scenario corresponding to the initial data identifier.

3. The method according to claim 1, characterized in that The step of determining a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes includes: The target adjustment mode is determined from the data adjustment modes based on the priorities of the data adjustment modes, the level selection conditions corresponding to the priorities, and the current system state value.

4. The method according to any one of claims 1 to 3, characterized in that If the target adjustment mode is the atomic adjustment mode, performing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result includes: In the atomic operation based on the local in-memory database, the first initial data value in the first data table is determined based on the target data identifier, and based on the first initial data value and the target adjustment value, data adjustment processing is performed to generate the data adjustment result, and the first data table is updated based on the data adjustment result; wherein, the first data table has idempotence.

5. The method according to any one of claims 1 to 3, characterized in that If the target adjustment mode is the transaction adjustment mode, performing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result includes: Initiate a first transaction through the first relational database, and determine a first shard location based on the target data identifier within the first transaction; Add a first pessimistic lock to the second data table and the first operation flow table stored in the first shard location, and insert a first adjustment record into the first operation flow table; wherein the second data table and the first operation flow table have idempotence; performing data adjustment processing based on the second initial data value in the second data table and the target adjustment value to generate the data adjustment result; The second data table and the first adjustment record are updated respectively based on the data adjustment result, the first transaction is committed, and the first pessimistic lock is released.

6. The method according to any one of claims 1 to 3, characterized in that If the target adjustment mode is the distributed adjustment mode, performing data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value to generate a data adjustment result includes: Initiate a second transaction through the first relational database, and determine a second shard location based on the target data identifier within the second transaction; Add a second pessimistic lock to the second operation flow table stored at the second shard location, and insert a second adjustment record into the second operation flow table; wherein the second operation flow table has idempotence; In the atomic operation based on the in-memory database, a third initial data value in a third data table is determined based on the target data identifier, and data adjustment processing is performed based on the third initial data value and the target adjustment value to generate the data adjustment result; wherein the third data table has idempotence; The third data table and the second adjustment record are updated respectively based on the data adjustment result, the second transaction is committed, and the second pessimistic lock is released.

7. The method according to any one of claims 1 to 3, characterized in that If the target adjustment mode is the atomic adjustment mode or the distributed adjustment mode, first configuration data and second configuration data are obtained, and when the first configuration data is different from the second configuration data, the configuration data corresponding to the target data identifier in the fourth data table stored in the in-memory database is updated based on the second configuration data; wherein, the second configuration data is the configuration data corresponding to the target data identifier last recorded in the second relational database corresponding to the business party, and the first configuration data is the configuration data corresponding to the target data identifier recorded before the configuration data update is executed in the in-memory database; the fourth data table is the first data table corresponding to the atomic adjustment mode or the third data table corresponding to the distributed adjustment mode.

8. A data processing method, characterized in that: include: generating an initial data identifier in response to a received data creation request; wherein the data creation request includes a target data value; Creating configuration data corresponding to the initial data identifier in the general data table based on the target data value; Based on the initial data identifier, the data synchronization request table corresponding to the user client is queried, and when it is determined through the data synchronization request table that the initial data identifier is not idempotent, a target adjustment mode adapted to the initial data identifier is determined from multiple data adjustment modes; wherein the data synchronization request table is used to record the data identifier, configuration data and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed at the near end, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on the collaboration between the memory database and the second relational database; The target data table corresponding to the target adjustment mode is updated using the initial data identifier and the configuration data corresponding to the initial data identifier.

9. The method according to claim 8, characterized in that The step of creating configuration data corresponding to the initial data identifier in the total data table based on the target data value includes: Opening a third transaction through the second relational database, and inserting data creation records into a third operation flow table based on the initial data identifier within the third transaction; When the initial data identifier and the target data value meet the idempotent condition, configuration data corresponding to the initial data identifier is created in the total data table based on the target data value, and after the data creation record is updated based on the configuration data corresponding to the initial data identifier, the third transaction is committed.

10. The method according to claim 9, characterized in that The updating of the target data table corresponding to the target adjustment mode by using the initial data identifier and the configuration data corresponding to the initial data identifier includes: A fourth transaction is opened through the second relational database. Within the fourth transaction, the target data table corresponding to the target adjustment mode is updated using the initial data identifier and the configuration data corresponding to the initial data identifier. After updating the data synchronization request table, the fourth transaction is committed.

11. The method according to any one of claims 8 to 10, characterized in that Before determining the target adjustment mode adapted to the initial data identifier from the multiple data adjustment modes, the method further includes: If it is determined that the initial data identifier corresponds to the periodic adjustment data, generating a periodic adjustment data fragment; In the periodic adjustment of the data slice, the step of determining a target adjustment mode adapted to the initial data identifier from a plurality of data adjustment modes is triggered.

12. The method according to any one of claims 8 to 10, characterized in that The method further comprises: Receive a data increment request; wherein the data increment request includes the initial data identifier and the target increment value; Opening a fifth transaction through the second relational database, and inserting a data increment record into the third operation flow table based on the initial data identifier within the fifth transaction; When the initial data identifier and the target incremental value satisfy the idempotent condition, updating the configuration data corresponding to the initial data identifier in the total data table using the target incremental value, and after updating the data incremental record based on the updated configuration data, committing the fifth transaction; querying the data synchronization request table based on the initial data identifier, and determining the target adjustment mode from the data adjustment modes when determining through the data synchronization request table that the initial data identifier is not idempotent; A sixth transaction is started through the second relational database. Within the sixth transaction, the target data table is updated using the initial data identifier and the target incremental value, and the sixth transaction is committed.

13. A data processing device, characterized in that: include: A request receiving module, configured to receive a data adjustment request; wherein the data adjustment request includes a target data identifier and a target adjustment value; A first adjustment mode determination module is configured to determine a target adjustment mode adapted to the target data identifier from a plurality of data adjustment modes; wherein the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a first relational database, or a distributed adjustment mode based on a collaboration between the memory database and the first relational database; The data adjustment module is configured to execute data adjustment processing corresponding to the target adjustment mode based on the target data identifier and the target adjustment value, and generate a data adjustment result.

14. A data processing device, characterized in that: include: an initial data identifier generating module, configured to generate an initial data identifier in response to a received data creation request; wherein the data creation request includes a target data value; A configuration data creation module, configured to create configuration data corresponding to the initial data identifier in the general data table based on the target data value; A second adjustment mode determination module is configured to query a data synchronization request table corresponding to the user client based on the initial data identifier, and when determining through the data synchronization request table that the initial data identifier is not idempotent, determine a target adjustment mode that is adapted to the initial data identifier from a plurality of data adjustment modes; wherein the data synchronization request table is configured to record the data identifier, configuration data, and synchronization status corresponding to the synchronization request; the data adjustment mode includes an atomic adjustment mode based on a memory database deployed proximally, a transaction adjustment mode based on a second relational database, or a distributed adjustment mode based on collaboration between the memory database and the second relational database; The target data table updating module is configured to update the target data table corresponding to the target adjustment mode using the initial data identifier and the configuration data corresponding to the initial data identifier.

15. An electronic device, characterized in that: include: processor; a memory for storing executable instructions; The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the data processing method according to any one of claims 1 to 12.

16. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the data processing method according to any one of claims 1 to 12.

17. A computer program product, characterized in that The computer program product is used to implement the data processing method according to any one of claims 1 to 12.

Images