CN113377557A - Service processing method and system and electronic equipment - Google Patents
Service processing method and system and electronic equipment Download PDFInfo
- Publication number
- CN113377557A CN113377557A CN202110744292.XA CN202110744292A CN113377557A CN 113377557 A CN113377557 A CN 113377557A CN 202110744292 A CN202110744292 A CN 202110744292A CN 113377557 A CN113377557 A CN 113377557A
- Authority
- CN
- China
- Prior art keywords
- message
- service
- state
- marking
- middleware system
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 22
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 64
- 238000012545 processing Methods 0.000 claims abstract description 57
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000012790 confirmation Methods 0.000 claims abstract description 34
- 238000012544 monitoring process Methods 0.000 claims description 8
- 230000002159 abnormal effect Effects 0.000 abstract description 6
- 230000026676 system process Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 14
- 238000012552 review Methods 0.000 description 8
- 238000002372 labelling Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1443—Transmit or communication errors
-
- 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/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Abstract
The application provides a business processing method, a business processing system and electronic equipment, which belong to the technical field of Internet, and the method comprises the following steps: the upstream service system processes the target service, sends the service message of the target service to the message middleware system (MQ system), monitors the operation event corresponding to the processing result of the target service if receiving the receiving confirmation information corresponding to the service message, and sends the state marking message of the service message to the message middleware system according to the operation event; the message middleware system acquires a state marking message corresponding to the service message, and marks the service message as a specified state based on the state marking message; wherein the designated states include a consumable state and a non-consumable state. The method and the device solve the problem that when the distributed system is used for processing the service, the abnormal service processing condition is caused by the conditions of the wrong sending, the missed sending and the like of the MQ message, and ensure the integrity of the service processing flow.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, and an electronic device for processing a service.
Background
In a complex business process involving multiple application systems, the business units are divided into multiple independent small business units A, B, C … … in units of systems. After the application system A finishes processing the service unit A, the application system A sends the MQ message to a message middleware system (MQ system), and the application system B starts to process the service unit B after receiving the MQ message sent by the MQ system. The application system A does not need to be strongly associated with the application system B when operating the service unit A, so that the complexity of the system can be reduced, the fault tolerance rate of the system can be improved, decoupling between the systems can be realized, and the consistency of data can be ensured.
However, in the above process, if a network anomaly occurs between the application system a and the MQ system or an application program anomaly occurs, the MQ system cannot receive the MQ message sent by the application system a, and the application system B cannot be triggered to process the service unit B, so that the MQ message is missed, and the service processing condition is abnormal.
If the service unit a rolls back, but the a application system sends the MQ message to the MQ system, the B application system starts to process the service unit B after receiving the MQ message sent by the MQ system, which causes the misdelivery of the MQ message and also causes the exception of the service processing.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, a system, and an electronic device for processing a service, which ensure accuracy and integrity of a service processing flow.
A first aspect of an embodiment of the present application provides a service processing method, which is applied to a message middleware system (MQ system), and includes:
acquiring a service message of a target service, and returning receiving confirmation information corresponding to the service message;
acquiring a state marking message corresponding to the service message, and changing the service message into a specified state based on the state marking message; wherein the designated states include a consumable state and a non-consumable state.
In an embodiment, the service processing method further includes:
scanning the service messages which are not changed into the designated state at regular time, and sending a search notice of the service messages;
and receiving a state marking message corresponding to the business message corresponding to the search notification, and marking the business message as a specified state based on the state marking message.
On the other hand, the present application further provides a service processing method, applied to an upstream service system, including:
processing the target service;
sending a service message of a target service to a message middleware system;
if receiving the receiving confirmation information corresponding to the service message, monitoring an operation event corresponding to the processing result of the target service;
and sending the state marking message of the service message to the message middleware system according to the operation event.
In an embodiment, the service processing method further includes:
and if the receiving confirmation message corresponding to the service message is not received, ending the processing of the target service.
In one embodiment, the operational events include rollback operational events and commit operational events.
Monitoring an operation event corresponding to a processing result of a target service, and sending a state marking message of a service message to a message middleware system according to the operation event, wherein the state marking message comprises the following steps:
if the operation event is a rollback operation event, sending a state marking message for marking the service message state as a non-consumable state to the message middleware system;
and if the operation event is a submitting operation event, sending a state marking message for marking the service message state as a consumable state to the message middleware system.
In an embodiment, the service processing method further includes:
acquiring a search notification, searching a service message indicated by the search notification in a local database, and acquiring a search result;
based on the search result, sending a state marking message of the service message corresponding to the search result to the message middleware system;
and receiving the marking confirmation information of the service message, and marking the service message in the local database as a submitted state.
In an embodiment, the service processing method further includes:
scanning uncommitted state service messages in a local database at regular time;
aiming at the business messages in the uncommitted state, sending a state marking message which marks the business messages in the uncommitted state as a consumable state to a message middleware system;
and when receiving a marking confirmation message returned by the message middleware system, marking the service message in the local database as a submitted state.
Further, the present application also provides a service processing method, applied to a downstream service system, including:
pulling a service message of a target service in a consumable state from a message middleware system;
and processing the associated service of the target service based on the service message.
Furthermore, the application also provides a service processing system, and the distributed service processing system comprises an upstream service system, a message middleware system and a downstream service system;
the upstream service system is used for processing the target service; sending a service message of a target service to a message middleware system; if receiving the receiving confirmation information corresponding to the service message, monitoring an operation event corresponding to the processing result of the target service; sending a state marking message of the service message to a message middleware system according to the operation event;
the message middleware system is connected with the upstream service system and used for acquiring the service message of the target service and returning the receiving confirmation information corresponding to the service message; acquiring a state marking message corresponding to the service message, and marking the service message as a specified state based on the state marking message; wherein the designated states include a consumable state and a non-consumable state;
the downstream business system is connected with the message middleware system and used for pulling the business message of the target business in a consumable state from the message middleware system; and processing the associated service of the target service based on the service message.
Finally, the present application also provides an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the service processing method.
In the technical solution provided by the foregoing embodiment of the present application, the MQ system performs state tagging on the MQ message sent by the upstream service system according to the service processing condition of the upstream service system, and determines whether the downstream service system can continue to perform service processing. The method avoids the condition that the abnormal business processing flow occurs due to the missending and the missed sending of the MQ message, and ensures the accuracy and the integrity of the business processing flow when the distributed system is used for processing the business.
Drawings
In order to more clearly explain the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that for those skilled in the art, other related drawings can be obtained from these drawings without inventive effort.
Fig. 1 is a schematic network architecture diagram of a distributed service processing system according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a service processing method according to an embodiment of the present application;
fig. 6 is a schematic flowchart of a message review method according to an embodiment of the present application;
fig. 7 is a schematic flowchart of a message review method according to another embodiment of the present application;
fig. 8 is a block diagram of a service processing apparatus according to an embodiment of the present application;
fig. 9 is a block diagram of a service processing apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Fig. 1 is a schematic network architecture diagram of a service processing system according to an embodiment of the present application. As shown in fig. 1, the service processing system includes an upstream service system 10, a message middleware system 20, and a downstream service system 30. The upstream service system 10, the message middleware system 20, and the downstream service system 30 are mounted on a server, a server cluster, or a cloud computing center.
Fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 2, the electronic device 40 includes: at least one processor 43 and a memory 41, one processor 43 being exemplified in fig. 2. Processor 43 and memory 41 are coupled via bus 42, and memory 41 stores instructions executable by processor 43, which instructions are executed by processor 43 to cause electronic device 40 to perform all or a portion of the processes described below as applied to upstream business system 10.
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 3, the electronic apparatus 50 includes: at least one processor 53 and a memory 51, one processor 53 being exemplified in fig. 3. Processor 53 and memory 51 are coupled via bus 52, and memory 51 stores instructions executable by processor 53, which instructions are executed by processor 53 to cause electronic device 50 to perform all or a portion of the processes described below as applied to message middleware system 20.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 4, the electronic device 60 includes: at least one processor 63 and a memory 61, one processor 63 being exemplified in fig. 3. Processor 63 and memory 61 are coupled via bus 62, and memory 61 stores instructions executable by processor 63, such that electronic device 60 may perform all or a portion of the processes described below as applied to downstream business system 30.
Fig. 5 is a flowchart illustrating a service processing method according to an embodiment of the present application. As shown in fig. 5, the method may include steps S510 to S550.
Step S510: the upstream service system processes the target service and sends a service message of the target service to the message middleware system.
The service message contains the target service content, when the upstream service system sends the service message to the message middleware system, the upstream service system indicates that the upstream service system starts to process the target service, and the service message is the MQ message.
When a distributed service system is applied to process services, the services are usually divided into a plurality of service units, and different service systems process corresponding service units, where a target service in this step is a service unit processed by an upstream service system.
For example, the services processed by the distributed service system are: and recommending and sharing commodity reward and recommending person point service. The method specifically comprises the following steps: and the user A purchases a commodity D under the trading system of the E-commerce platform C through the commodity link shared by the user B, and after payment is successful, the user B obtains a corresponding recommended credit in the credit system of the E-commerce platform. Then the service is split into two independent service units, which are:
service unit A: the user A completes payment operation for purchasing the commodity D in the transaction system;
service unit B: the bonus point system adds a corresponding bonus point to the user B.
The upstream service system processes the service unit A, the downstream service system processes the service unit B, and the target service in the above steps is the service unit A.
In an embodiment, the upstream service system may process multiple target services simultaneously and send multiple service messages to the message middleware system simultaneously.
Step S520: the message middleware system acquires the service message of the target service and returns a receiving confirmation message of the service message to the upstream service system.
After receiving the service message, the message middleware system returns corresponding receiving confirmation information to the upstream service system, and represents that the message middleware system has received the service message.
In one embodiment, the upstream traffic system may determine whether it has received a receipt acknowledgement message.
If the upstream service system does not receive the receiving confirmation message, ending the processing of the target service;
and if the upstream service system receives the receiving confirmation message, continuing the corresponding service operation.
The mode ensures that the MQ message can be accurately sent to the message middleware system, and avoids the condition of missing sending of the MQ message.
In an embodiment, the message middleware system may obtain a plurality of service messages of the target service at the same time, and return the reception confirmation information of the plurality of service messages at the same time.
Step S530: and the upstream service system monitors the operation event corresponding to the processing result of the target service.
When the upstream service system receives the receiving confirmation message of the service message, the upstream service system can continue to monitor the operation event corresponding to the processing result of the target service.
When the upstream service system receives the receiving confirmation information of the service message, the processing result of the target service is obtained, and corresponding service operation is carried out on the target service according to the processing result of the target service. In the application, the service operation performed on the target service is referred to as an operation event, and the upstream service system monitors the operation event in real time and acquires the type of the operation event in real time.
In an embodiment, the acceptance confirmation information includes a target service number, which is convenient for the upstream service system to obtain a processing result of the target service.
Step S540: the upstream service system sends a state marking message of the service message to the message middleware system according to the operation event, the message middleware system acquires the state marking message of the service message, and marks the service message as a designated state based on the state marking message, wherein the designated state comprises a consumable state and a non-consumable state.
The operation events are specifically divided into a submitting operation event and a rollback operation event, the submitting operation event is a processing result of the upstream service system for receiving the target service, and the distributed service system is agreed to continue to perform the service process; and if the rollback operation event is that the processing result of the target service is abnormal, the upstream service system does not accept the processing result of the target service, and the target service is cancelled, so that the service flow is terminated.
And the upstream service system sends a state marking message of the service message to the message middleware system according to the type of the operation event, wherein the state marking message is a message notification and informs the message middleware system to mark the service message as a specified state, and the specified state comprises a consumable state and a non-consumable state. For any one service message, the service message may be marked as consumable or non-consumable.
When the operation event type is a rollback operation event, the upstream service system sends a state marking message to the message middleware system and informs the message middleware system to mark the service message as a non-consumable state; when the operation event type is the submitting operation event, the upstream service system sends a state marking message to the message middleware system and informs the message middleware system to mark the service message as a consumable state.
The service message in the consumable state can be acquired by a downstream service system, so that the downstream service system executes corresponding service operation; the service message in the non-consumable state can not be acquired by a downstream service system, and the service flow is terminated.
In an embodiment, the upstream service system may send a plurality of status labeling messages to the message middleware system at the same time, and the message middleware system may also obtain status labeling messages of the plurality of service messages at the same time, and label the corresponding service messages as a consumable status or a non-consumable status based on the plurality of status labeling messages, respectively.
In an embodiment, the receiving confirmation message of the service message includes a service message number, and the upstream service system may send a status marking message to the message middleware system according to the service message number, and notify the message middleware system to mark the service message as a designated status.
In an embodiment, before the upstream service system sends the status annotation message to the message middleware system, the service message corresponding to the commit operation event is stored in the local database.
In an embodiment, when the message middleware system marks the service message as a consumable state, the message middleware system sends a marking confirmation message to an upstream service system, and the upstream service system receives the marking confirmation message and marks the corresponding service message in the local database as a submitted state.
In an embodiment, the message middleware system may send multiple marking confirmation messages to the upstream service system at the same time, and the upstream service system receives multiple marking confirmation messages at the same time, and marks multiple service messages in the local database as a submitted state.
Step S550: the downstream service system pulls the service message of the target service in a consumable state from the message middleware system, and processes the associated service of the target service based on the service message.
When the downstream service system successfully draws the service message in a consumable state, the downstream service system indicates that the upstream service system has finished processing the target service, and the downstream service system can process the associated service of the target service.
In an embodiment, the downstream service system may determine whether to pull the service message, pull the service message again when the pulling fails, and continue to execute the corresponding service operation when the pulling succeeds.
In one embodiment, the upstream business system may pull multiple business messages in consumable state from the message middleware system at the same time.
In an embodiment, the downstream service system may obtain the service number from the service message, and process the associated service of the target service based on the service number.
In one embodiment, the downstream traffic system can process multiple traffic simultaneously.
Fig. 6 is a flowchart illustrating a message review method according to an embodiment of the present application. As shown in fig. 6, the message review method includes steps S610 to S630.
When the distributed service system processes the service, the system may have network abnormality, which causes the service message not to be marked as the designated state, so that the service flow is forced to be interrupted. Therefore, the application provides a message review method, so that the service flow forced to be interrupted due to network abnormity is recovered to run.
Step S610: the message middleware system regularly scans the service messages which are not changed into the designated state, and sends service message searching notification to an upstream service system.
The designated state comprises a consumable state and an unconsumed state, if the system network is normal, the message middleware system marks the local service message as the designated state, and if the message middleware system has the service message which is not marked as the designated state, the network abnormality occurs at the moment.
When network abnormity occurs, the message middleware system sends a searching notice of the service message which is not changed into the designated state to the upstream service system, and the upstream service system searches whether the service message is stored in the local database, so that the corresponding operation event type of the service message can be determined.
In one embodiment, the message middleware system periodically scans the service messages, obtains the service message numbers, and determines whether the service messages are stored in the local database of the upstream service system.
In an embodiment, the MQ system may send the search notification of multiple service messages to the upstream service system simultaneously, and obtain the numbers of multiple service messages simultaneously.
Step S620: the upstream service system acquires a search notification, searches the service message indicated by the search notification in a local database, and acquires a search result; and sending the state marking message of the service message to the message middleware system based on the searching result.
The search result specifically includes the following two types: if the service message indicated by the search notification is stored in the local database, the corresponding operation event type of the service message is a submission operation event; and if the service message is not stored in the local database, the corresponding operation event type of the service message is a rollback operation event.
And the upstream service system sends the state marking message of the service message to the message middleware system based on the search result.
Step S630: and the message middleware system receives the state marking message sent by the upstream service system and marks the service message as an appointed state based on the state marking message.
Wherein the designated states include a consumable state and a non-consumable state.
In an embodiment, when the service message is marked in a consumable state, the message middleware system sends a marking confirmation message of the service message to the upstream service system, and the upstream service system receives the marking confirmation message and marks the service message in the local database in a submitted state, so as to facilitate the back check of the service message when the network is abnormal, and the related content refers to the following related description, which is not described herein again.
After the system in this embodiment performs step S630, the downstream service system also performs step S550 in the above embodiment, and the corresponding content is the same as that in the embodiment described in fig. 5, and is not described again here.
Fig. 7 is a flowchart illustrating a message review method according to another embodiment of the present application. As shown in fig. 7, the message review method includes steps S710 to S720.
The message rechecking method in the embodiment can recover the service processing flow which is forced to be interrupted when the network is abnormal.
The method comprises the steps that a local database of an upstream business system stores business messages corresponding to submission operation events, when a message middleware system marks the business messages in a consumable state, the business messages in the local database are marked in a submitted state, the submission operation of the business messages is completed in the mode, and the submission operation is corresponding operation which enables the business messages to be acquired by a downstream business system.
However, if a network anomaly occurs in the above process, the message middleware system fails to mark the service message as a consumable state, and the service message in the local database is not marked as a committed state, so that the service process is forced to be interrupted, and the system has a network anomaly when the service message in an uncommitted state exists in the local database.
Step S710: the upstream business system periodically scans the business messages in the local database in an uncommitted state.
The uncommitted state traffic message removes a portion of the committed state traffic message from the local database.
Step S720: the upstream business system sends a state marking message marking the business message in an uncommitted state to the message middleware system aiming at the business message in the uncommitted state, and the message middleware system receives the state marking message and marks the business message in a consumable state.
In an embodiment, the message middleware system returns a label confirmation message to the upstream service system, and the upstream service system receives the label confirmation message and marks the service message in the uncommitted state in the local database as committed.
It is seen that, the purpose of marking the service message in the upstream service system as a committed state in step S540 and step S630 in the foregoing embodiment is to facilitate the execution of the message review method in this embodiment.
Fig. 8 is a service processing apparatus according to an embodiment of the present application. As shown in fig. 8, the service processing apparatus is applied to the message middleware system 20, and the service processing apparatus includes a message obtaining module 810, i.e., a status marking module 820.
The message obtaining module 810 is configured to obtain a service message of the target service, and return reception confirmation information corresponding to the service message.
And a status labeling module 820, configured to obtain a status labeling message corresponding to the service message, and label the service message as a specified status based on the status labeling message.
Fig. 9 is a service processing apparatus according to an embodiment of the present application. As shown in fig. 9, the service processing apparatus is applied to the upstream service system 10, and the service processing apparatus includes a service execution module 910, a message sending module 920, an event monitoring module 930, and a status notification module 940.
And the service execution module 910 is configured to process the target service.
A message sending module 920, configured to send a service message of the target service to the message middleware system.
The event monitoring module 930 is configured to monitor an operation event corresponding to a processing result of the target service when receiving the reception confirmation information corresponding to the service message.
And a status notification module 940, configured to send a status labeling message of the service message to the message middleware system according to the operation event.
In the several embodiments provided in the present application, the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (10)
1. A service processing method applied to a message middleware system (MQ system), comprising:
acquiring a service message of a target service, and returning a receiving confirmation message corresponding to the service message;
acquiring a state marking message corresponding to the service message, and marking the service message as a specified state based on the state marking message; wherein the designated states include a consumable state and a non-consumable state.
2. The traffic processing method according to claim 1, wherein the method further comprises:
scanning the service messages which are not changed into the designated state at regular time, and sending a search notice of the service messages;
and receiving the state marking message of the service message indicated by the search notification, and marking the service message as an appointed state based on the state marking message.
3. A service processing method is applied to an upstream service system, and is characterized by comprising the following steps:
processing the target service;
sending the service message of the target service to a message middleware system;
if receiving a receiving confirmation message corresponding to the service message, monitoring an operation event corresponding to a processing result of the target service;
and sending the state marking message of the service message to the message middleware system according to the operation event.
4. The traffic processing method according to claim 3, wherein the method further comprises:
and if the receiving confirmation message corresponding to the service message is not received, finishing the processing of the target service.
5. The business processing method of claim 3, wherein the operational events comprise rollback operational events and commit operational events;
the monitoring an operation event corresponding to a processing result of the target service, and sending a state marking message of the service message to a message middleware system according to the operation event includes:
if the operation event is a rollback operation event, sending a state marking message for marking the service message as a non-consumable state to the message middleware system;
and if the operation event is a submitting operation event, sending a state marking message for marking the service message as a consumable state to the message middleware system.
6. The traffic processing method according to claim 3, wherein the method further comprises:
obtaining a search notification, searching a service message indicated by the search notification in a local database, and obtaining a search result;
based on the search result, sending the state marking message of the service message corresponding to the search result to the message middleware system;
and receiving a marking confirmation message of the service message, and marking the service message in the local database as a submitted state.
7. The traffic processing method according to claim 3, wherein the method further comprises:
scanning uncommitted state service messages in a local database at regular time;
sending a state marking message marking the business message in the uncommitted state as a consumable state to the message middleware system;
and when receiving a marking confirmation message returned by the message middleware system, marking the service message in the local database as a submitted state.
8. A service processing method is applied to a downstream service system, and is characterized by comprising the following steps:
pulling a service message of a target service in a consumable state from a message middleware system;
and processing the associated service of the target service based on the service message.
9. A transaction system, comprising:
an upstream service system, a message middleware system and a downstream service system;
the upstream service system is used for processing the target service; sending the service message of the target service to the message middleware system; if receiving the receiving confirmation information corresponding to the service message, monitoring an operation event corresponding to the processing result of the target service; sending a state marking message of the service message to the message middleware system according to the operation event;
the message middleware system is connected with the upstream service system and used for acquiring the service message of the target service and returning the receiving confirmation information corresponding to the service message; acquiring the state marking message corresponding to the service message, and marking the service message as a specified state based on the state marking message; wherein the designated states include a consumable state and a non-consumable state;
the downstream business system is connected with the message middleware system and used for pulling the business message of the target business in the consumable state from the message middleware system; and processing the associated service of the target service based on the service message.
10. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the traffic processing method of any of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110744292.XA CN113377557A (en) | 2021-07-01 | 2021-07-01 | Service processing method and system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110744292.XA CN113377557A (en) | 2021-07-01 | 2021-07-01 | Service processing method and system and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113377557A true CN113377557A (en) | 2021-09-10 |
Family
ID=77580471
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110744292.XA Pending CN113377557A (en) | 2021-07-01 | 2021-07-01 | Service processing method and system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113377557A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114119019A (en) * | 2021-11-26 | 2022-03-01 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
| CN115412208A (en) * | 2022-08-09 | 2022-11-29 | 唯阜德(武汉)科技有限公司 | Message transmission method and system for message queue management system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040898A1 (en) * | 2012-07-31 | 2014-02-06 | Alan H. Karp | Distributed transaction processing |
| CN109684045A (en) * | 2017-10-18 | 2019-04-26 | 阿里巴巴集团控股有限公司 | Processing method, device and the electronic equipment of transaction message |
| CN111666162A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Distributed message transmission method, device, computer equipment and storage medium |
| CN112559223A (en) * | 2020-12-24 | 2021-03-26 | 京东数字科技控股股份有限公司 | Message sending method, device, equipment and computer readable storage medium |
-
2021
- 2021-07-01 CN CN202110744292.XA patent/CN113377557A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040898A1 (en) * | 2012-07-31 | 2014-02-06 | Alan H. Karp | Distributed transaction processing |
| CN109684045A (en) * | 2017-10-18 | 2019-04-26 | 阿里巴巴集团控股有限公司 | Processing method, device and the electronic equipment of transaction message |
| CN111666162A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Distributed message transmission method, device, computer equipment and storage medium |
| CN112559223A (en) * | 2020-12-24 | 2021-03-26 | 京东数字科技控股股份有限公司 | Message sending method, device, equipment and computer readable storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114119019A (en) * | 2021-11-26 | 2022-03-01 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
| CN114119019B (en) * | 2021-11-26 | 2024-03-12 | 跨境银行间支付清算有限责任公司 | Multi-channel access method and device based on cross-border payment system |
| CN115412208A (en) * | 2022-08-09 | 2022-11-29 | 唯阜德(武汉)科技有限公司 | Message transmission method and system for message queue management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100555269C (en) | Be used for announcing and monitoring method and the device that distributed data processing system provides the entity of service | |
| CN113377557A (en) | Service processing method and system and electronic equipment | |
| KR100943110B1 (en) | Trading system | |
| US9639885B2 (en) | Recovery of e-commerce orders | |
| AU2010305653B2 (en) | Delivery with reconciliation on client side | |
| CN111640265B (en) | Method, system and equipment for positioning card retaining and account error of self-service equipment | |
| CN108762895B (en) | Method and device for processing distributed transaction | |
| CN111367934B (en) | Data consistency checking method, device, server and medium | |
| CN114841710B (en) | Method, device, equipment and medium for removing order when transaction system fails | |
| CN109493230B (en) | Supplementary recording method and device for unilateral transaction | |
| JP2007025807A (en) | Questionnaire system | |
| CN114612204A (en) | Account checking method and device | |
| CN112990871A (en) | Document processing method and related equipment | |
| CN111835566A (en) | System fault management method, device and system | |
| CN113204561A (en) | Method for keeping consistency of data of multi-system and multi-system adopting method | |
| CN108874621B (en) | File monitoring method and device, electronic equipment and computer readable storage medium | |
| JPH06195571A (en) | Commodity sale data processor | |
| CN114066648B (en) | Cross-service multi-service type data processing method and related equipment | |
| US20220164733A1 (en) | Event monitoring with support system integration | |
| CN116431872B (en) | Observable system and service observing method based on observable system | |
| CN113379484B (en) | Method, system, equipment and medium for quick matching of orders | |
| CN115496583A (en) | Asynchronous accounting data processing method, device, equipment and storage medium | |
| CN116401129A (en) | Service system monitoring method, device, terminal and storage medium | |
| CN116051108A (en) | Payment processing method, device, equipment and storage medium | |
| CN116126590A (en) | Data processing method, device, electronic equipment and storage medium |
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 |