CN117370457A - Multithreading data real-time synchronization method, equipment and medium - Google Patents
Multithreading data real-time synchronization method, equipment and medium Download PDFInfo
- Publication number
- CN117370457A CN117370457A CN202311257941.9A CN202311257941A CN117370457A CN 117370457 A CN117370457 A CN 117370457A CN 202311257941 A CN202311257941 A CN 202311257941A CN 117370457 A CN117370457 A CN 117370457A
- Authority
- CN
- China
- Prior art keywords
- message
- data
- producer
- synchronization
- sending
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000012544 monitoring process Methods 0.000 claims abstract description 9
- 230000002618 waking effect Effects 0.000 claims abstract description 6
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 8
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 238000013507 mapping Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 7
- 238000003672 processing method Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000033772 system development Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24578—Query processing with adaptation to user needs using ranking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a multithreading data real-time synchronization method, equipment and medium, wherein the method comprises the following steps: the method comprises the steps of determining message data corresponding to service information through a producer, sending the message data to a data synchronization service component, obtaining corresponding producer message stream data, sending monitoring events of message timing sending threads, waking up the message timing sending threads in a semaphore control thread number mode, sending the message data to a message queue corresponding to a message synchronization theme, determining a consumer subscription theme, pulling out the message data in the message queue, consuming the message data, and storing the consumer message stream data. The method and the device realize real-time synchronization of multithreaded data, realize execution of related operations in a single instance, and prevent data inconsistency caused by concurrency problems, thereby ensuring the accuracy of data synchronization, add a message timing sending thread, and carry out compensation sending on unsent messages so as to ensure the atomicity and sequence consistency of data operation.
Description
Technical Field
The application relates to the field of micro services in software system development, in particular to a method, equipment and medium for real-time synchronization of multithreaded data.
Background
In the field of micro services in current software system development, there is a micro service architecture that splits an application into a set of small services, and each service is focused on completing a specific business function and is mutually matched through a lightweight communication mechanism, where different services correspond to different business databases.
As services become more complex, more and more data is being served, and more data centers or nodes are required to store and process data, a highly available and reliable data synchronization service is needed to ensure that data between nodes remains synchronized.
The data synchronization service refers to a process of copying data from one system to another, and a key point in the process is to ensure the atomicity and sequential consistency of data operations, which are difficult to realize in the field of micro services in the current software system development.
Disclosure of Invention
In order to solve the above problems, the present application proposes a method for real-time synchronization of multithreaded data, including:
determining message data corresponding to service information through a producer, and sending the message data to a data synchronization service component;
acquiring producer message stream data corresponding to the message data through the data synchronization service component, and issuing a monitoring event of a message timing sending thread;
starting a monitor of a message timing sending thread, waking up the message timing sending thread in a semaphore control thread quantity mode, and pulling the producer message flow data at fixed time;
traversing the producer message stream data, transmitting the message data from the data synchronization component to a message queue corresponding to a message synchronization topic based on different data types, and updating the producer message stream data based on the message synchronization topic;
determining that a consumer subscribes to the message synchronization subject, pulling message data in a message queue of the message synchronization subject through the consumer, consuming the message data according to the message sending sequence in the producer message stream data, and storing the consumer message stream data.
In another aspect, the present application further proposes a multithreaded data real-time synchronization device, including:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the multithreaded data real-time synchronization method described in the above example.
In another aspect, the present application also proposes a non-volatile computer storage medium storing computer-executable instructions configured to: the multithreaded data real-time synchronization method described in the above example.
The multi-thread data real-time synchronization method provided by the application can bring the following beneficial effects:
the multi-thread data real-time synchronization is realized based on the distributed message queue middleware system, the related operation of a single instance is limited to be executed through a distributed lock in the micro-service system, the data inconsistency caused by the concurrency problem is prevented, and meanwhile, the access sequence of the node to the resource is controlled, so that the accuracy of the data synchronization is ensured.
And a message timing sending thread is added, when abnormal data sending occurs, the message timing sending thread can carry out compensation sending on unsent messages until the message sending is successful, thereby ensuring the reliability of data synchronization to the maximum extent, ensuring the atomicity of data operation, carrying out exclusive operation in a distributed lock mode, avoiding the error condition that two application services compensate the same data at the same time, and ensuring the high availability of data synchronization.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1 is a flow chart of a method for real-time synchronization of multithreaded data according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a producer flow of a method for real-time synchronization of multi-threaded data according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a consumer flow chart of a method for real-time synchronization of multi-threaded data according to an embodiment of the present application;
fig. 4 is a schematic diagram of a multi-threaded data real-time synchronization device according to an embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, an embodiment of the present application provides a method for real-time synchronization of multithreaded data, including:
s101: and determining message data corresponding to the service information through the producer, and sending the message data to a data synchronization service component.
In the micro-service architecture, each micro-service has own service logic and completes own specific service functions, so that each service has own data storage in the service corresponding to the micro-service, and when the data needs to be shared among the micro-services, the data among the services are shared and synchronized through the data synchronization technology. The method provided in the embodiments of the present application is implemented based on an open source distributed message queue middleware system (e.g., a dockmq system, a Kafka system, a rubbi tMQ system, etc., and the description is explained in the description using, for example, the dockmq system to explain the method provided by the application), including components of a producer, a consumer, a topic, a message queue contained in the topic, a message server, etc.
Specifically, as shown in fig. 2, in the service component, corresponding service information (for example, information such as a payment account, a payment amount, a payment time, a payment result, etc. of the service information of the payment service) is determined according to the service, and message data required to perform the service operation is determined according to the service information.
Further, the message data is constructed by the producer and the message data object is constructed based on the message data, so that the message data is conveniently operated on in the subsequent process, and the message data is sent to the data synchronization service component by using the message data object.
S102: and obtaining producer message stream data corresponding to the message data through the data synchronization service component, and issuing a monitoring event of a message timing sending thread.
As shown in FIG. 2, in the process of a producer sending message data to a data synchronization service component, producer message pipeline data is obtained and saved to a corresponding producer pipeline table in a database.
The producer message stream data (in some cases, as shown in fig. 2, which may also be referred to as producer stream records) includes a unique identifier of the message data, a sending time, a content of the message data, a data type, a sending status, a sending record, a target subject, and the like, and ensures that one message stream data is stored under the same transaction.
Meanwhile, a monitoring event of a message timing sending thread is issued in the data synchronization service component to monitor the abnormality or failure occurring in the data synchronization process, so that the temporary interruption of message sending is caused, the data is repaired or compensated through the message timing sending thread, and the unsent message is compensated and sent, so that the consistency and accuracy of the data and the atomicity of the data operation are ensured.
S103: starting a monitor of the message timing sending thread, waking up the message timing sending thread by a semaphore control thread quantity mode, and pulling the producer message flow data at fixed time.
Starting a monitor of a message timing sending thread, calling a scheduledThreadPoolExecutor class, initializing the message timing sending thread, and waking up the message timing sending thread in a signal quantity mode, wherein the scheduledThreadPoolExecutor class is used for executing a timing task, and the message timing sending thread is a timing compensation task designed based on the scheduledThreadPoolExecutor class and comprises functions of processing and sending a message sequence, updating a message running record state, waking up retries and the like.
Specifically, the number of threads is controlled through semaphores, a semaphore object is created, the initial value of the semaphore object is set to 0, and at the moment, in the process of sending the threads at message timing, the threads are in a waiting state; when the message timing sending thread needs to be awakened, for example, when a new message needs to be sent, a related function is called to release the semaphore, and when the value of the semaphore is larger than 0, the message timing sending thread is awakened, and a message timing compensation task is executed.
Further, as shown in fig. 2, the time interval is set in a self-defined manner, the sending frequency of the message data in the producer message stream data and the record number of the message data sending in the time interval (in some scenarios, the message data in the producer stream water meter is also called as the timing pull data synchronous stream data as shown in fig. 2) are pulled regularly, the unsent message data in the database is scanned, the unsent message data is sent in a compensating manner until the final sending is successful, the exclusive operation is performed in a distributed lock manner, the error condition that two application services compensate the same data simultaneously is avoided, and the high availability of the data synchronization and the atomicity of the data operation are ensured.
S104: traversing the producer message stream data, transmitting the message data from the data synchronization component to a message queue corresponding to a message synchronization topic based on different data types, and updating the producer message stream data based on the message synchronization topic.
Specifically, traversing producer message stream data, obtaining the content and the data type of message data sent to a data synchronization component, determining a designated theme of message data sending according to different data types, obtaining a message queue of the theme according to the designated theme, sending the message data from the data synchronization component to the message queue corresponding to the message synchronization theme, at the moment, sending the message data to the message queue, updating the sending state and the sending record of the message data in the producer message stream data, and updating the data in the producer stream meter in a database.
When the sending task of the message data is processed, based on the distributed lock, only one instance is limited to execute the sending task at any moment, and after the sending task of the instance is completed, the distributed lock is released, so that other instances can acquire the lock and execute the corresponding tasks, and the global sequence of the message data synchronization is ensured.
Further, after the message data is sent from the data synchronization component to the message queue corresponding to the message synchronization subject, the message sent by the message data is sent to the corresponding message queue, so that the message queue determines that the data is received.
Further, when the message data is not normally sent or the message timing sending thread is abnormal, the time is set by user definition, the record number in the producer message flow data is read in the time period, the message data which is not sent in the producer flow water meter is scanned, the unsent message data is subjected to compensation sending, and the unsent message data is resent to the corresponding message queue until the final sending is successful; when the message timing sending thread is abnormal, but after the flow list of the producer is scanned, the message timing sending thread is directly exited from the task when the unsent message data is not found, and the next awakening is to be retried.
S105: determining that a consumer subscribes to the message synchronization subject, pulling message data in a message queue of the message synchronization subject through the consumer, consuming the message data according to the message sending sequence in the producer message stream data, and storing the consumer message stream data.
As shown in fig. 3, a message synchronization topic is subscribed to by a consumer, a message queue within the subscribed topic is determined, synchronization message data is pulled from the message queue to a data synchronization component, and processing prior to consuming the data is performed in the data synchronization component.
Specifically, a RocketMq consumer listener implementation class is defined to monitor whether a new message arrives, a corresponding service implementation class is queried according to a message type, a message consumer basic abstract class is called, and a corresponding server implementation class is queried according to different data types to realize the consumption operation of the message data.
The method comprises the steps of providing a message consumer basic abstract class, wherein member variables or methods of the message consumer basic abstract class comprise application program context objects, a business service object mapping set, message entry processing definition, consumption retry monitoring realization and the like, the business service object mapping set is internally defined with data types of message data and realization class lists of message consumer basic class interfaces, the message consumer basic class interfaces comprise three interface methods, namely a doHandle method, a handleMessagetype method and a handleConsummerclass method, the doHandle method is a template method for carrying out actual business processing on the message data, specific realization logic is provided by subclasses of the method, the handleMessagetype method returns the data types, and the handleConsummerclass returns the associated RocketMq consumer listener realization class.
According to the data type in the service object mapping set, the service object is obtained from the application program context object and stored in the service object mapping set, and the message processing method of the message consumption entry service class object is called through the default message processing entry method provided by the message consumer basic abstract class, or the method can be rewritten in the custom consumer subclass according to the actual requirement, so as to realize the corresponding service logic.
The consumption retry monitoring implementation function includes: the method comprises the steps of realizing an onMessage method of a class interface by a RocketMq consumer listener, setting the retry times of consuming message data, and carrying out exception handling when the maximum retry times are reached.
Further, a consumption flow water meter in a database is obtained, a message consumption entry service class is called, and whether the current message data exist in the consumption flow water meter is judged according to the unique identifier of the message flow data of the consumer, wherein the consumption flow water meter comprises the unique identifier of the message flow data of the consumer, the unique identifier of the message data, the unique identifier of the consumer, the consumption record, the consumption state and other information.
If the current message data does not exist, calling a specific consumer service class, realizing three interface methods in a message consumer base class interface, returning to an associated RocketMq consumer monitor realization class, calling the specific consumer service class according to different data types, processing corresponding service logic, judging whether a current service database routing key is matched with a configuration value of a data synchronization service or not, executing a consuming operation on the current message data when the matching is determined, storing the current message data into a service table in a database, and storing the unmatched message into a consumption flow water meter in the database when the unmatched message is determined.
If the current message data exists, the message data is indicated to have undergone the consumption operation and the consumption record is stored in the consumption flow water meter, and then the message of which the current message data has been normally consumed is submitted to the message queue, so that the repeated consumption of the message data is prevented, and the idempotency of the message synchronization is ensured.
As shown in fig. 4, the embodiment of the present application further proposes a multithreaded data real-time synchronization device, including:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the multithreaded data real-time synchronization method described in the above example.
The embodiments also provide a non-volatile computer storage medium storing computer executable instructions configured to: the multithreaded data real-time synchronization method described in the above example.
All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for the apparatus and medium embodiments, the description is relatively simple, as it is substantially similar to the method embodiments, with reference to the section of the method embodiments being relevant.
The devices and media provided in the embodiments of the present application are in one-to-one correspondence with the methods, so that the devices and media also have similar beneficial technical effects as the corresponding methods, and since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media are not described in detail herein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (10)
1. A method for real-time synchronization of multi-threaded data, comprising:
determining message data corresponding to service information through a producer, and sending the message data to a data synchronization service component;
acquiring producer message stream data corresponding to the message data through the data synchronization service component, and issuing a monitoring event of a message timing sending thread;
starting a monitor of a message timing sending thread, waking up the message timing sending thread in a semaphore control thread quantity mode, and pulling the producer message flow data at fixed time;
traversing the producer message stream data, transmitting the message data from the data synchronization component to a message queue corresponding to a message synchronization topic based on different data types, and updating the producer message stream data based on the message synchronization topic;
determining that a consumer subscribes to the message synchronization subject, pulling message data in a message queue of the message synchronization subject through the consumer, consuming the message data according to the message sending sequence in the producer message stream data, and storing the consumer message stream data.
2. The method according to claim 1, wherein the message data in the message queue of the message synchronization topic is pulled by the consumer, and the message data is consumed according to the message sending sequence in the producer message stream data, specifically comprising:
defining a RocketMq consumer listener implementation class, calling a message consumer basic abstract class, and inquiring a corresponding server implementation class according to the different data types to realize the consumption operation of the message data;
acquiring a consumption flow water meter in a database, calling a message consumption entry service class, and judging whether current message data exist in the consumption flow water meter;
if the current message data does not exist, invoking a specific consumer service class, judging whether a service database routing key corresponding to the current theme is matched with a configuration value of a data synchronization service, executing a consumption operation on the current message data when the matching is confirmed, storing the current message data into a service table in a database, and storing the unmatched message into the consumption flow water meter in the database when the unmatched message is confirmed;
if the current message data exists, submitting the message of which the current message data is normally consumed to the message queue.
3. The method of claim 2, wherein invoking the message consumer base abstract class queries a corresponding server implementation class based on the different data types, comprising:
the method for determining the basic abstract class of the message consumer comprises the steps of application program context object, business service object mapping set, message entry processing definition and consumption retry monitoring realization;
acquiring a business service object from the application program context object according to the data type in the business service object mapping set and storing the business service object into the business service object mapping set;
the message entry process definition specifically includes: calling a message consumption entry service class, and custom rewriting a message processing method to realize custom business logic;
the consumption retry monitoring specifically includes: setting the retry number of consumption of the message data, and performing exception handling when the maximum retry number is reached.
4. The method according to claim 1, wherein traversing the producer message stream data, based on different data types, sending the message data from the data synchronization component to a message queue of a corresponding message synchronization topic, and updating the producer message stream data based on the message synchronization topic, comprises:
traversing the producer message stream data, controlling a single instance to execute a sending task based on a distributed lock, and sending the message data to a message queue corresponding to a message synchronization subject according to different data types;
updating the sending state of the message data in the producer message stream data based on the message synchronization subject, and sending the message sent by the message data to the corresponding message queue.
5. The method according to claim 4, wherein the method further comprises:
when the message data is not normally sent or the message timing sending thread is abnormal, compensating the message data and resending the message data to the corresponding message queue;
when the message timing sending thread is abnormal and has no data to be compensated, the message timing sending thread can return to the sleep state again to wait for the next awakening.
6. The method according to claim 1, wherein producer message stream data is obtained by the producer sending the message data to a data synchronization service component, comprising in particular:
generating the message data by a producer, sending the message data to a data synchronization service component, obtaining producer message flow data, and storing the producer message flow data into a producer flow meter in a database;
determining that the same transaction stores a message stream data, wherein the message stream data is producer message stream data or consumer message stream data.
7. The method according to claim 5, wherein when the message data is not normally sent or the message timing sending thread is abnormal, the message data is compensated and resent to the corresponding message queue, specifically including:
when the message timing sending thread is abnormal, the user-defined setting reads the record number and the read time interval in the producer message flow data, scans the message data which is not sent in the producer flow water meter, carries out compensation sending, and resends the message data to the corresponding message queue until the final sending is successful.
8. The method according to claim 2, wherein obtaining a consumption flow meter in a database, calling a message consumption entry service class, and determining whether current message data exists in the consumption flow meter, comprises:
acquiring a consumption flow water meter in a database, calling a message consumption entry service class, and judging whether current message data exist in the consumption flow water meter according to the unique identifier of the message flow data of the consumer;
and if the consumption business logic does not exist, executing the consumption business logic, and inserting the consumption record into a consumption flow water meter.
9. A multi-threaded data real-time synchronization device, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: a method of real-time synchronization of multi-threaded data as claimed in any one of claims 1 to 8.
10. A non-transitory computer storage medium storing computer-executable instructions, the computer-executable instructions configured to: a method of real-time synchronization of multi-threaded data as claimed in any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311257941.9A CN117370457B (en) | 2023-09-26 | Multithreading data real-time synchronization method, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311257941.9A CN117370457B (en) | 2023-09-26 | Multithreading data real-time synchronization method, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117370457A true CN117370457A (en) | 2024-01-09 |
| CN117370457B CN117370457B (en) | 2024-07-09 |
Family
ID=
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338773A (en) * | 2020-02-21 | 2020-06-26 | 华云数据有限公司 | Distributed timed task scheduling method, scheduling system and server cluster |
| CN111555957A (en) * | 2020-03-26 | 2020-08-18 | 孩子王儿童用品股份有限公司 | Kafka-based synchronous message service system and implementation method |
| WO2020238365A1 (en) * | 2019-05-31 | 2020-12-03 | 深圳前海微众银行股份有限公司 | Message consumption method, apparatus and device, and computer storage medium |
| CN112667414A (en) * | 2020-12-23 | 2021-04-16 | 平安普惠企业管理有限公司 | Message queue-based message consumption method and device, computer equipment and medium |
| CN114116259A (en) * | 2021-11-24 | 2022-03-01 | 浪潮软件股份有限公司 | Message queue-based real-time message pushing method, system, device and medium |
| CN115665191A (en) * | 2022-10-09 | 2023-01-31 | 浪潮云信息技术股份公司 | User information synchronization method and system based on cloud storage system |
| CN116319988A (en) * | 2023-03-21 | 2023-06-23 | 浪潮通用软件有限公司 | Data processing method, system, storage medium and equipment |
| CN116382943A (en) * | 2023-03-28 | 2023-07-04 | 上海非码网络科技有限公司 | Sequential message processing method, bus system, computer device, and storage medium |
| CN116467091A (en) * | 2023-03-08 | 2023-07-21 | 平安壹钱包电子商务有限公司 | Message processing method, device, equipment and medium based on message middleware |
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020238365A1 (en) * | 2019-05-31 | 2020-12-03 | 深圳前海微众银行股份有限公司 | Message consumption method, apparatus and device, and computer storage medium |
| CN111338773A (en) * | 2020-02-21 | 2020-06-26 | 华云数据有限公司 | Distributed timed task scheduling method, scheduling system and server cluster |
| CN111555957A (en) * | 2020-03-26 | 2020-08-18 | 孩子王儿童用品股份有限公司 | Kafka-based synchronous message service system and implementation method |
| CN112667414A (en) * | 2020-12-23 | 2021-04-16 | 平安普惠企业管理有限公司 | Message queue-based message consumption method and device, computer equipment and medium |
| CN114116259A (en) * | 2021-11-24 | 2022-03-01 | 浪潮软件股份有限公司 | Message queue-based real-time message pushing method, system, device and medium |
| CN115665191A (en) * | 2022-10-09 | 2023-01-31 | 浪潮云信息技术股份公司 | User information synchronization method and system based on cloud storage system |
| CN116467091A (en) * | 2023-03-08 | 2023-07-21 | 平安壹钱包电子商务有限公司 | Message processing method, device, equipment and medium based on message middleware |
| CN116319988A (en) * | 2023-03-21 | 2023-06-23 | 浪潮通用软件有限公司 | Data processing method, system, storage medium and equipment |
| CN116382943A (en) * | 2023-03-28 | 2023-07-04 | 上海非码网络科技有限公司 | Sequential message processing method, bus system, computer device, and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| 张杰、满曙光等: "采用消息队列实现数据一致性方法", 《计算机应用》, vol. 28, no. 9, 15 September 2019 (2019-09-15) * |
| 杨成荣;刘峻松;孙新杰;吴超;: "基于微服务架构的数据一致性方法研究", 电脑知识与技术, no. 08, 15 March 2020 (2020-03-15) * |
| 谭喆: "《应用软件开发协议栈》", vol. 1, 31 March 2020, 东南大学出版社, pages: 437 - 442 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106790694B (en) | Distributed system and scheduling method of target object in distributed system | |
| US8938421B2 (en) | Method and a system for synchronizing data | |
| US11681683B2 (en) | Transaction compensation for single phase resources | |
| JPH05197604A (en) | Multiprocessor computer and operating method thereof | |
| CN110611707B (en) | Task scheduling method and device | |
| US8464269B2 (en) | Handling and reporting of object state transitions on a multiprocess architecture | |
| CN112445598B (en) | Task scheduling method and device based on quartz, electronic equipment and medium | |
| US9553929B2 (en) | Episodic coordination model for distributed applications | |
| CN112148436B (en) | Decentralised TCC transaction management method, device, equipment and system | |
| CN112597249A (en) | Synchronous distribution and storage method and system for service data | |
| US6185702B1 (en) | Method and system for process state management using checkpoints | |
| CN112925614A (en) | Distributed transaction processing method, device, medium and equipment | |
| CN113094362A (en) | Method and device for reliably delivering and processing asynchronous message | |
| CN111352704B (en) | Distributed global transaction processing system and method based on policy management | |
| CN115994053A (en) | Parallel playback method and device of database backup machine, electronic equipment and medium | |
| CN112559496B (en) | Method and device for realizing transaction atomicity of distributed database | |
| CN117370457B (en) | Multithreading data real-time synchronization method, equipment and medium | |
| CN111930492B (en) | Task flow scheduling method and system based on decoupling task data model | |
| CN112231073A (en) | Distributed task scheduling method and device | |
| CN117370457A (en) | Multithreading data real-time synchronization method, equipment and medium | |
| JP4920567B2 (en) | Equipment network system and data access control method | |
| JP2003242313A (en) | Business progress controller and method thereof, business progress control program, and recording medium recorded with the program | |
| CN114138364A (en) | Application information loading control system and application information loading method | |
| CN113900840A (en) | Distributed transaction final consistency processing method and device | |
| CN112162840A (en) | Coroutine processing and managing method based on interrupt reentrant mechanism |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |