Data processing method and device, electronic equipment and computer readable medium
By listening to subscription events and generating reconciliation tasks, calling the reconciliation engine to perform reconciliation tasks, the problem of inconsistent core data in the retail system is solved, the accuracy and speed of business processing is improved, and the system stability is improved.
Patent Information
- Application Number
- CN202310538554.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-12
AI Technical Summary
Due to the complexity of multi-system connection and data synchronization in existing retail systems, core data is inconsistent among multiple systems, reducing business processing efficiency and accuracy.
Obtain system identification and pending data by listening to subscription events, determine business methods and execution strategies based on subscription events and system identification, generate reconciliation tasks, and call reconciliation engine to perform reconciliation tasks, trigger alarm processes and automatic repair programs to ensure data consistency.
It improves the accuracy and speed of business processing, improves the stability and operation and maintenance efficiency of the system.
Smart Images

Figure CN118941300A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of e-commerce technology, and in particular to a data processing method, device, electronic device and computer-readable medium. Background Art
[0002] At present, in order to provide customers with a purchase experience that is indiscriminate (uniform price, uniform service quality) at any time, any place, and any way, current retail companies are embracing omni-channel retail, that is, combining sales through as many channels as possible, including offline physical stores, public domain platforms, private domain platforms, various information media, and all channels that can generate sales. As the retail business continues to expand and move forward, the supporting technical systems will become more and more complex, involving the connection and integration of multiple systems. Due to the large number of systems involved, the long data synchronization links, the different operation and maintenance capabilities and stability of each system, coupled with network failures, imperfect system fault tolerance processing, system logic bugs and other reasons, the core data of retail (such as goods, prices, inventory, orders) is likely to be inconsistent in multiple systems, thereby reducing business processing efficiency and accuracy. Summary of the invention
[0003] In view of this, embodiments of the present application provide a data processing method, device, electronic device and computer-readable medium, which can solve the problem that the core data of existing retail may be inconsistent in multiple systems, thereby reducing business processing efficiency and accuracy.
[0004] To achieve the above objective, according to one aspect of an embodiment of the present application, a data processing method is provided, including:
[0005] In response to monitoring a subscription event, obtaining a corresponding system identifier and data to be processed;
[0006] Based on the subscription events and system identifiers, the corresponding business methods and execution strategies are determined, and then reconciliation tasks are generated based on the data to be processed;
[0007] The reconciliation engine is called to execute the reconciliation task. In response to the task execution result that there is inconsistent data, an alarm process is triggered, the alarm type is determined, and then the corresponding automatic repair program is executed according to the alarm type.
[0008] Optionally, before obtaining the corresponding system identifier, the method further includes:
[0009] In response to detecting a data change, a subscription event is triggered.
[0010] Optionally, generate a reconciliation task, including:
[0011] Determine the source system ID and the target system ID according to the system ID;
[0012] Generate corresponding reconciliation tasks based on the data to be processed, source system ID, target system ID, business method and execution strategy.
[0013] Optionally, after executing the corresponding automatic repair program, the method further includes:
[0014] Visually display the automatic repair result data on the data dashboard.
[0015] Optionally, the data to be processed is obtained by following the steps below:
[0016] Get the link ID corresponding to the subscription event;
[0017] Asynchronously obtain the data corresponding to the link identifier as the data to be processed.
[0018] Optionally, asynchronously acquiring data corresponding to the link identifier as data to be processed includes:
[0019] The front-end application is called to access the log center to obtain the data corresponding to the link identifier, and then the obtained data is determined as the data to be processed.
[0020] Optionally, the data processing method further includes:
[0021] Send the acquired data to be processed to the message queue; and
[0022] Generate reconciliation tasks based on the data to be processed, including:
[0023] Call the message consumer to obtain the data to be processed from the message queue to execute the reconciliation task generation process.
[0024] In addition, the present application also provides a data processing device, including:
[0025] An acquisition unit, configured to acquire a corresponding system identifier and data to be processed in response to monitoring a subscription event;
[0026] The task generation unit determines the corresponding business method and execution strategy based on the subscription event and system identifier, and then generates a reconciliation task based on the data to be processed;
[0027] The execution unit is configured to call the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, trigger the alarm process, determine the alarm type, and then execute the corresponding automatic repair program according to the alarm type.
[0028] Optionally, the acquisition unit is further configured to:
[0029] In response to detecting a data change, a subscription event is triggered.
[0030] Optionally, the task generation unit is further configured to:
[0031] Determine the source system ID and the target system ID according to the system ID;
[0032] Generate corresponding reconciliation tasks based on the data to be processed, source system ID, target system ID, business method and execution strategy.
[0033] Optionally, the data processing device further includes a visualization display unit configured to:
[0034] Visually display the automatic repair result data on the data dashboard.
[0035] Optionally, the acquisition unit is further configured to:
[0036] Get the link ID corresponding to the subscription event;
[0037] Asynchronously obtain the data corresponding to the link identifier as the data to be processed.
[0038] Optionally, the acquisition unit is further configured to:
[0039] The front-end application is called to access the log center to obtain the data corresponding to the link identifier, and then the obtained data is determined as the data to be processed.
[0040] Optionally, the data processing device further includes a sending unit configured to:
[0041] Send the acquired data to be processed to the message queue; and
[0042] The task generation unit is further configured to:
[0043] Call the message consumer to obtain the data to be processed from the message queue to execute the reconciliation task generation process.
[0044] In addition, the present application also provides a data processing electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the data processing method as described above.
[0045] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the data processing method as described above is implemented.
[0046] One embodiment of the above invention has the following advantages or beneficial effects: the application obtains the corresponding system identifier and the data to be processed in response to monitoring the subscription event; determines the corresponding business method and execution strategy based on the subscription event and the system identifier, and then generates a reconciliation task based on the data to be processed; calls the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, triggers the alarm process, determines the alarm type, and then executes the corresponding automatic repair program according to the alarm type. Thereby improving the accuracy and speed of business processing.
[0047] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.
[0049] Figure 1 It is a schematic diagram of the main process of a data processing method provided according to an embodiment of the present application;
[0050] Figure 2 It is a schematic diagram of the main process of a data processing method provided according to an embodiment of the present application;
[0051] Figure 3 It is a logical diagram of a reconciliation platform of a data processing method provided according to an embodiment of the present application;
[0052] Figure 4 It is a schematic diagram of an inspection mechanism for omni-channel core transaction data according to a data processing method provided in one embodiment of the present application;
[0053] Figure 5 is a schematic diagram of main units of a data processing device according to an embodiment of the present application;
[0054] Figure 6 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;
[0055] Figure 7 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION
[0056] The following is an explanation of the exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the technical solution of the present disclosure, the collection, collection, update, analysis, processing, use, transmission, storage and other aspects of user personal information involved are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Take necessary measures for user personal information to prevent illegal access to user personal information data and maintain user personal information security, network security and national security.
[0057] Figure 1 is a schematic diagram of the main flow of a data processing method provided according to an embodiment of the present application, such as Figure 1 As shown, the data processing method includes:
[0058] Step S101, in response to monitoring a subscription event, obtaining a corresponding system identifier and data to be processed.
[0059] In this embodiment, the execution subject of the data processing method (for example, a server) can determine whether to monitor the subscription event through a wired connection or a wireless connection. The mechanism for triggering the subscription event can be detecting a change in data. After monitoring the subscription event, the execution subject can obtain the system identifier associated with the subscription event. The system identifier can include a source system identifier (for example, A) and a target system identifier (for example, B).
[0060] Specifically, before obtaining the corresponding system identifier, the data processing method further includes: in response to detecting a data change, triggering a subscription event. The data change may include data increase or data decrease.
[0061] Specifically, the data to be processed is obtained through the following steps: obtaining a link identifier corresponding to a subscription event; and asynchronously obtaining data corresponding to the link identifier as the data to be processed.
[0062] The link corresponding to the subscription event may be, for example, a commodity sales link, a price customization link, an inventory count link, etc. The embodiment of the present application does not specifically limit the link corresponding to the subscription event. The link identifier corresponding to the subscription event may be, for example, a link name or a link number, etc. The embodiment of the present application does not specifically limit the link identifier. The data corresponding to the link identifier is obtained by asynchronous execution as the data to be processed, so that each link has its own unified interface, and no intrusion into the business code is achieved.
[0063] Specifically, asynchronously obtaining data corresponding to the link identifier as the data to be processed includes: calling the front-end application to access the log center to obtain the data corresponding to the link identifier, and then determining the obtained data as the data to be processed. The log center cleans and calculates the data, and finally records the standard synchronous data into the ElasticSearch storage.
[0064] Step S102, based on the subscription event and the system identifier, determine the corresponding business method and execution strategy, and then generate a reconciliation task based on the data to be processed.
[0065] A business method may be, for example, a business execution step. An execution strategy may be, for example, the specific execution logic of each step during business execution.
[0066] Step S103, calling the reconciliation engine to execute the reconciliation task, in response to the task execution result that there is inconsistent data, triggering the alarm process, determining the alarm type, and then executing the corresponding automatic repair program according to the alarm type.
[0067] If the reconciliation engine finds inconsistent data after executing the reconciliation task, it can be considered as a potential error record and will be stored separately. The error handling module will trigger a system alarm. At the same time, for system failure errors, it will trigger automatic repair (the synchronization program of the business system can be called), and then a second check will be performed.
[0068] Specifically, after executing the corresponding automatic repair program, the method also includes: visually displaying the automatic repair result data on the data dashboard.
[0069] This embodiment obtains the corresponding system identifier and pending data in response to monitoring the subscription event; determines the corresponding business method and execution strategy based on the subscription event and system identifier, and then generates a reconciliation task based on the pending data; calls the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, triggers the alarm process, determines the alarm type, and then executes the corresponding automatic repair program according to the alarm type. This improves the accuracy and speed of business processing.
[0070] Figure 2 is a schematic diagram of the main flow of a data processing method provided according to an embodiment of the present application, such as Figure 2 As shown, the data processing method includes:
[0071] Step S201, in response to monitoring a subscription event, obtaining a corresponding system identifier and data to be processed.
[0072] When the increase or decrease of data is detected, the subscription event is triggered to obtain the corresponding system identification and the data to be processed. The system identification may include the source system identification and the target system identification. The data in the system corresponding to the source system identification may be synchronized to the system corresponding to the target system identification.
[0073] Step S202: Determine the corresponding business method and execution strategy based on the subscription event and the system identifier.
[0074] Step S203: determining the source system identifier and the target system identifier according to the system identifier.
[0075] The system identifier may include a source system identifier and a target system identifier. The system corresponding to the source system identifier contains data to be synchronized. The data to be synchronized is synchronized to the system corresponding to the target system identifier to achieve data synchronization.
[0076] Step S204, generating a corresponding reconciliation task according to the data to be processed, the source system identifier, the target system identifier, the business method and the execution strategy.
[0077] The task creation program is called to generate a corresponding reconciliation task according to the data to be processed, the source system identifier, the target system identifier, the business method, and the execution strategy. The reconciliation task can be an asynchronous task.
[0078] Step S205, calling the reconciliation engine to execute the reconciliation task, in response to the task execution result that there is inconsistent data, triggering the alarm process, determining the alarm type, and then executing the corresponding automatic repair program according to the alarm type.
[0079] Specifically, the data processing method also includes: sending the acquired data to be processed to a message queue; and generating a reconciliation task based on the data to be processed, including: calling a message consumer program to obtain the data to be processed from the message queue to execute the reconciliation task generation process.
[0080] The data collection program is responsible for collecting data from each process node of the original program, sending the collected data to the message queue to complete the data reporting. The log center is responsible for cleaning and calculating the data, and finally recording the standard synchronization data into the ElasticSearch storage.
[0081] Figure 3 Schematic diagram of an application scenario of a data processing method provided by an embodiment of the present application. The data processing method of the embodiment of the present application can be applied to scenarios where data is synchronized. Data synchronization types include: product addition, product modification, store product addition, modification, status change, price, and inventory change. Figure 3As shown, the reconciliation platform monitors the events sent by the target system (such as system A, system B, system C) as the event source, matches the rules defined in the rule management center, and selects and executes the corresponding execution strategy, and outputs the execution result to complete the main process of reconciliation. Among them, the rule management center also includes the following parts: alarm strategy, alarm recipient, rule status management, and alarm status management. Alarm strategy can be divided into telephone, email, internal OA and other methods. Rule status and alarm status management can enable or disable rules and alarms. Business rules are business methods in the embodiments of the present application. The business rule executor is an indispensable component of the reconciliation center. The executor parses the data to be obtained (such as goods, prices, inventory, order data, etc.) through the execution strategy, obtains the required data from each corresponding system, and completes the comparison of business data according to the execution script or calling the set interface. The execution strategy can be carried by scripts and interfaces, where the script supports multiple languages, such as Groovy, Python, etc. In addition to selecting script execution, you can also configure the API interface provided by a system to complete more complex reconciliation calculations. The execution result is the closing link in the reconciliation life cycle. The execution result completes the alarm through the alarm strategy and the alarm recipient. In addition, each execution result will be saved, and the historical comparison results can be queried. In terms of visualization, the platform also provides a data dashboard function to discover problem trends, determine whether the problem is converged, and provide decision-making references for users. Data synchronization is triggered by messages, such as new products, product modifications, store product additions, modifications, status changes, prices, inventory changes, etc., and data synchronization is completed through data acquisition, data conversion, data transmission, and result collection. Each link has its own unified interface. In order to avoid intrusion into the business code, the data of each link is asynchronously collected based on JavaAgent technology. The data collection program is responsible for collecting data from each process node of the original program, sending the collected data to the message queue to complete the data reporting, and the log center is responsible for cleaning and calculating the data, and finally recording the standard synchronization data to the ElasticSearch storage. Users complete the retrieval of logs by accessing the front-end application, and the front-end program obtains the original data by accessing the log center to complete the data visualization. The embodiment of the present application provides a transaction data inspection mechanism for omni-channel cross-system interactions, establishes a universal reconciliation platform, opens up system alarm capabilities, opens up data repair tools for business systems, and makes synchronization log tracks persistent and searchable, which can greatly improve operation and maintenance efficiency and further improve system stability.
[0082] Figure 4It is a schematic diagram of the inspection mechanism of omni-channel core transaction data according to the data processing method provided by an embodiment of the present application. In the embodiment of the present application, ERP system: Enterprise Resource Planning System (Enterprise Resource Planning) refers to a management platform based on information technology, which provides decision-making and operation means for enterprise decision-makers and employees with systematic management ideas. RPC: Remote Procedure Call, it is a protocol that requests services from a remote computer program through the network without understanding the underlying network technology. MQ: Message Queue (Message Queue), generally used to solve problems such as application decoupling, asynchronous messaging, and traffic peak shaving, to achieve high performance, high availability, scalability and eventual consistency architecture. Elastic Search: It is a distributed, highly scalable, and highly real-time search and data analysis engine. It can easily enable large amounts of data to have the ability to search and analyze.
[0083] like Figure 4 As shown, the execution subject for implementing the data processing method implements the following parts:
[0084] Universal reconciliation platform: Regardless of the transaction data such as goods, prices, inventory, promotions, and orders, data inconsistencies across systems can be discovered through inspections through the reconciliation mechanism. The value of the universal reconciliation platform lies in the unified construction of reusable capabilities in the reconciliation process to create platform capabilities. The reusable capabilities include: establishing reconciliation scenarios and rules, calling the data query module in the business module to perform data comparison on the data in the source system A and the target system B, storing and post-processing the comparison results (such as triggering system alarms), etc. Personalized capabilities for specific business scenarios (such as specific reconciliation rules) can be opened to the business in a scripted manner.
[0085] Visual query of synchronization log track: Call the data synchronization module in source system A to synchronize the log records of data, which is used to store the process data and results of each synchronization, and is equipped with a visualization page to facilitate business retrieval and self-service processing of synchronization differences.
[0086] A third-party public package for business system integration: used by source system A. After the introduction of this public package, source system A can quickly integrate the ability to report synchronization logs and trigger real-time reconciliation.
[0087] Specifically, the management end of the universal reconciliation platform is used to manage reconciliation scenarios, define the data sources of both parties of the reconciliation (it can be a database, an RPC interface, or a message body in the data change MQ), define the reconciliation scope (which fields need to be compared by calling the data comparison program, how to define whether the fields are consistent, etc.), and configure the reconciliation cycle (the cycle for executing reconciliation at a fixed time can be configured, such as once every hour).
[0088] Reconciliation engine of the general reconciliation platform: After the management end establishes the reconciliation task, the reconciliation engine will execute the scheduling of the reconciliation task, including parsing the reconciliation configuration information, extracting the reconciliation data from the data source (supporting business configuration of the data source or implementing the data extraction script yourself), executing the reconciliation strategy, and persisting the reconciliation results for retrieval.
[0089] Error handling of the general reconciliation platform: Inconsistent data found by the reconciliation engine is considered to be a potential error record and will be stored separately. The error handling module will trigger a system alarm. At the same time, for errors caused by system failures, it will trigger an automatic data repair program (which can call the synchronization program of the business system) and then perform a secondary check.
[0090] Figure 5 Schematic diagram of the main units of the data processing device according to an embodiment of the present application. Figure 5 As shown, the data processing device 500 includes an acquisition unit 501 , a task generation unit 502 and an execution unit 503 .
[0091] The acquisition unit 501 is configured to acquire the corresponding system identifier and the data to be processed in response to monitoring the subscription event.
[0092] The task generation unit 502 determines the corresponding business method and execution strategy based on the subscription event and the system identifier, and then generates a reconciliation task based on the data to be processed.
[0093] The execution unit 503 is configured to call the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, trigger the alarm process, determine the alarm type, and then execute the corresponding automatic repair program according to the alarm type.
[0094] In some embodiments, the acquisition unit 501 is further configured to: trigger a subscription event in response to detecting a data change.
[0095] In some embodiments, the task generation unit 502 is further configured to: determine the source system identifier and the target system identifier based on the system identifier; and generate a corresponding reconciliation task based on the data to be processed, the source system identifier, the target system identifier, the business method, and the execution strategy.
[0096] In some embodiments, the data processing device further includes Figure 5 The visualization display unit not shown in the figure is configured to: visualize the automatic repair result data on the data dashboard.
[0097] In some embodiments, the acquisition unit 501 is further configured to: acquire a link identifier corresponding to a subscription event; and asynchronously acquire data corresponding to the link identifier as data to be processed.
[0098] In some embodiments, the acquisition unit 501 is further configured to: call the front-end application to access the log center to acquire data corresponding to the link identifier, and then determine the acquired data as data to be processed.
[0099] In some embodiments, the data processing device further includes Figure 5 The sending unit not shown in the figure is configured to: send the acquired data to be processed to the message queue; and the task generation unit is further configured to: call the message consumption program to obtain the data to be processed from the message queue to execute the reconciliation task generation process.
[0100] It should be noted that the data processing method and the data processing device of the present application have a corresponding relationship in terms of specific implementation contents, so the repeated contents will not be described again.
[0101] Figure 6 An exemplary system architecture 600 to which the data processing method or data processing device according to the embodiment of the present application can be applied is shown.
[0102] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, 603, network 604 and server 605. Network 604 is used to provide a medium for communication links between terminal devices 601, 602, 603 and server 605. Network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0103] Users can use terminal devices 601, 602, and 603 to interact with server 605 through network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).
[0104] The terminal devices 601 , 602 , and 603 may be various electronic devices having a data processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.
[0105] Server 605 can be a server that provides various services, such as a background management server that provides support for subscription events monitored by users using terminal devices 601, 602, and 603 (only as an example). The background management server can obtain the corresponding system identifier and data to be processed in response to monitoring the subscription event; determine the corresponding business method and execution strategy based on the subscription event and the system identifier, and then generate a reconciliation task based on the data to be processed; call the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, trigger the alarm process, determine the alarm type, and then execute the corresponding automatic repair program according to the alarm type. Thereby improving the accuracy and speed of business processing.
[0106] It should be noted that the data processing method provided in the embodiment of the present application is generally executed by the server 605 , and accordingly, the data processing device is generally set in the server 605 .
[0107] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0108] Reference below Figure 7 , which shows a schematic diagram of the structure of a computer system 700 of a terminal device suitable for implementing an embodiment of the present application. Figure 7 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0109] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the computer system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.
[0110] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage section 708 as needed.
[0111] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a 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 part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the system of the present application are executed.
[0112] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable storage media may include, for example, but are not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. 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 or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, 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 appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0113] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing 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 from the order 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 or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0114] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes an acquisition unit, a task generation unit, and an execution unit. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0115] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device responds to listening to the subscription event, obtains the corresponding system identification and data to be processed; based on the subscription event and the system identification, determines the corresponding business method and execution strategy, and then generates a reconciliation task based on the data to be processed; calls the reconciliation engine to execute the reconciliation task, and in response to the task execution result that there is inconsistent data, triggers the alarm process, determines the alarm type, and then executes the corresponding automatic repair program according to the alarm type.
[0116] According to the technical solution of the embodiment of the present application, the accuracy and speed of business processing can be improved.
[0117] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.
Claims
1. A data processing method, It is characterized in that include: In response to monitoring a subscription event, obtaining a corresponding system identifier and data to be processed; Based on the subscription event and the system identifier, a corresponding business method and an execution strategy are determined, and then a reconciliation task is generated based on the data to be processed; The reconciliation engine is called to execute the reconciliation task, and in response to the task execution result that inconsistent data exists, an alarm process is triggered, the alarm type is determined, and then a corresponding automatic repair program is executed according to the alarm type.
2. The method according to claim 1, It is characterized in that Before obtaining the corresponding system identifier, the method further includes: In response to detecting a data change, a subscription event is triggered.
3. The method according to claim 1, It is characterized in that The generating of the reconciliation task includes: Determine a source system identifier and a target system identifier according to the system identifier; A corresponding reconciliation task is generated according to the data to be processed, the source system identifier, the target system identifier, the business method and the execution strategy.
4. The method according to claim 1, It is characterized in that After executing the corresponding automatic repair program, the method further includes: Visually display the automatic repair result data on the data dashboard.
5. The method according to claim 1, It is characterized in that The data to be processed is obtained by following the steps below: Obtaining the link identifier corresponding to the subscription event; Asynchronously obtain data corresponding to the link identifier as data to be processed.
6. The method according to claim 5, It is characterized in that The asynchronously acquiring the data corresponding to the link identifier as the data to be processed includes: The front-end application is called to access the log center to obtain the data corresponding to the link identifier, and then the obtained data is determined as the data to be processed.
7. The method according to claim 1, It is characterized in that The method further comprises: Sending the acquired data to be processed to a message queue; and The generating of the reconciliation task based on the data to be processed includes: The message consumption program is called to obtain the data to be processed from the message queue to execute the reconciliation task generation process.
8. A data processing device, It is characterized in that Configured to: An acquisition unit, configured to acquire a corresponding system identifier and data to be processed in response to monitoring a subscription event; A task generation unit, which determines a corresponding business method and execution strategy based on the subscription event and the system identifier, and further generates a reconciliation task based on the data to be processed; The execution unit is configured to call the reconciliation engine to execute the reconciliation task, trigger an alarm process in response to the task execution result that there is inconsistent data, determine the alarm type, and then execute a corresponding automatic repair program according to the alarm type.
9. The device according to claim 8, It is characterized in that The acquisition unit is further configured to: In response to detecting a data change, a subscription event is triggered.
10. The device according to claim 8, It is characterized in that The task generation unit is further configured to: Determine a source system identifier and a target system identifier according to the system identifier; A corresponding reconciliation task is generated according to the data to be processed, the source system identifier, the target system identifier, the business method and the execution strategy.
11. A data processing electronic device, It is characterized in that Configured to: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the apparatus as described in any one of claims 1 to 7.
12. A computer readable medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the apparatus according to any one of claims 1 to 7 is implemented.
Citation Information
Cited By
Data proofreading method and device and readable storage medium
CN119762257A
