Cross-system data synchronization method and device

Abstract

The invention provides a cross-system data synchronization method and device. The method comprises the steps of performing unified asynchronous event monitoring on various actions which may cause changes in transaction order data on a first system end, obtaining a transaction order ID in which the data changes occur, and putting the transaction ID and a first system ID into a Redis collection; ona second system end, reading the data in the Redis collection every preset time period; when reading the data, according to the transaction order ID in the Redis collection, requesting the first system end OpenAPI by HTTP to obtain transaction order detail data corresponding to the transaction order ID; on the first system end, returning the transaction order detail data in a unified format by using the OpenAPI; on the second system end, acquiring and parsing the transaction order detail data, writing to a database of the second system end, or updating a cache. The method can reduce the coupling dependence among different systems and can ensure the timeliness and accuracy of data synchronization among the systems.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a cross-system data synchronization method and device. Background technique [0002] Under the current circumstances, there is a transaction order data sharing problem between the transaction business B-end system and the transaction C-end system. The transaction B-end will create a transaction order, and the business personnel will record the transaction process through the transaction B-end system, and the transaction C-end system needs to obtain it synchronously The process data of these transaction orders are simultaneously displayed on the transaction C-end APP, so that users can intuitively view the details and precautions of their own related business processing progress. [0003] At present, the data synchronization of transaction B-side and C-side transaction order process data mainly has the following disadvantages: 1. Share the same database (C-side directly connects...

AI Technical Summary

Problems solved by technology

[0003] At present, the data synchronization of transaction B-side and C-side transaction order process data mainly has the following disadvantages: 1. Share the same database (C-side directly connects to query the B-side database), and the change of transaction B-side data structure will affect the adjustment of transaction C-side data acquisition logic , the transaction C-end system is strongly coupled with the transaction B-end system, and if there is a problem with the transaction B-end system DB, both the transaction B and C-end systems will be affected

In addition, 2. Non-shared databases adopt a data timing synchronization scheme, data timing synchronization, data change synchronization is not timely, and the efficiency of DB full data synchronization is low

Images