CN111090532B - Application service calling method, device, electronic equipment and computer storage medium - Google Patents
Application service calling method, device, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN111090532B CN111090532B CN201911283987.1A CN201911283987A CN111090532B CN 111090532 B CN111090532 B CN 111090532B CN 201911283987 A CN201911283987 A CN 201911283987A CN 111090532 B CN111090532 B CN 111090532B
- Authority
- CN
- China
- Prior art keywords
- message
- processing
- task data
- processing state
- state
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000012545 processing Methods 0.000 claims abstract description 160
- 238000004891 communication Methods 0.000 claims description 15
- 238000006243 chemical reaction Methods 0.000 claims description 2
- 238000004590 computer program Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 2
- 230000002411 adverse Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 238000006467 substitution reaction Methods 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a calling method of application service, a device thereof, electronic equipment and a computer storage medium. The method comprises the following steps: sending a service call message to a first message queue, wherein the service call message carries an identification number for distinguishing different service call messages; the service call message is taken out from the first message queue, converted into task data and stored in a database, and the processing state of the task data is marked as an initial state; the task data is taken out from the database, converted into a message entity and sent to a second message queue; retrieving and processing the message entity from the second message queue; and updating the processing state of the task data according to the processing result of the message entity. The call path and processing state can be determined by carrying an identification number throughout the entire message asynchronous process flow in the service call message.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for calling an application service, an electronic device, and a computer storage medium.
Background
With the continuous development of electronic information technology, many enterprises widely use MQ services (services implemented based on AMQP (Advanced Message Queuing Protocol) protocol, such as rabkitmq) to perform asynchronous processing of messages, so as to realize decoupling between different systems.
However, the applicant found in the course of implementing the present invention that the prior art has the following problems: the MQ server can only provide the final processing state if a message is invoked between multiple application service systems.
When the processing state of the processing failure finally occurs, the specific reason of the message processing failure cannot be determined according to the MQ (message queue) server, and the retry operation cannot be directly performed, so that the adverse effect is caused on the calling of the application service.
Disclosure of Invention
The embodiment of the invention provides a calling method of application service, a device thereof, electronic equipment and a computer storage medium, which are used for solving one or more problems existing in the existing calling process of the application service.
A first aspect of an embodiment of the present invention provides a method for calling an application service. Wherein the method comprises the following steps:
sending a service call message to a first message queue, wherein the service call message carries an identification number for distinguishing different service call messages;
the service call message is taken out from the first message queue, converted into task data and stored in a database, and the processing state of the task data is marked as an initial state;
the task data is taken out from the database, converted into a message entity and sent to a second message queue;
retrieving and processing the message entity from the second message queue;
and updating the processing state of the task data according to the processing result of the message entity.
Optionally, the updating the processing state of the task data according to the processing result of the message entity specifically includes:
according to the processing result, the processing state of the task data is sent to a third message queue;
and searching matched task data in the database through the identification number and updating the processing state of the matched task data.
Optionally, the processing state includes: a first processing state for indicating that the message entity processing is successful and notifying the caller, a second processing state for indicating that the message entity processing is successful but not notifying the caller, a third processing state for indicating that the message entity processing is successful but also a subsequent processing flow, and a failure state that the message entity processing is unsuccessful.
Optionally, the method further comprises: converting the task data with the processing state being the second processing state into a message entity according to a preset time period in a timing polling mode, and sending the message entity into a fourth message queue; and updating the processing state of the task data into a first processing state.
Optionally, after updating the processing state of the task data according to the processing result of the message entity, the method further includes:
and after receiving the retry instruction, recovering the task data with the processing state of failure to an initial state.
Optionally, task data with the processing state being the initial state is taken out from the database according to a preset time period in a timing polling mode.
Optionally, the identification number remains unchanged during the process of converting the service call message into task data and a message entity, where the task data and the message entity both carry the identification number.
The second aspect of the embodiment of the invention provides a calling device of application service. Wherein the device comprises:
the service application module is used for sending service calling information to the first information queue, wherein the service calling information carries identification numbers for distinguishing different service calling information; the first scheduling service module is used for taking out the service call message from the first message queue, converting the service call message into task data and storing the task data in a database, wherein the processing state of the task data is marked as an initial state; the second scheduling service module is used for taking out the task data from the database, converting the task data into a message entity and sending the message entity into a second message queue; the application service module is used for taking out the message entity from the second message queue and processing the message entity; and the third scheduling service module is used for updating the processing state of the task data according to the processing result of the message entity.
A third aspect of an embodiment of the present invention provides an electronic device. The electronic equipment comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to perform the steps of the method of invoking an application service as described above.
A fourth aspect of the embodiments of the present invention provides a non-volatile computer storage medium having stored therein at least one computer program for causing a processor to execute the steps of the method for invoking an application service described above.
According to the application service calling method provided by the embodiment of the invention, the specific calling path of the service calling message can be determined by carrying the identification number which penetrates through the whole message asynchronous processing flow in the service calling message, and the specific processing state can be clarified, so that the position and the reason of failure can be conveniently positioned when the processing fails.
The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and may be implemented according to the content of the specification, so that the technical means of the embodiments of the present invention can be more clearly understood, and the following specific embodiments of the present invention are given for clarity and understanding.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an application service invocation method provided by an embodiment of the present invention;
fig. 2 is a schematic diagram of an application scenario for executing the application service invocation method shown in fig. 1 according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a change in processing status of a message provided by an embodiment of the present invention;
FIG. 4 is a functional block diagram of an application service invocation apparatus provided by an embodiment of the present invention;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Fig. 1 shows a flowchart of a method for calling an application service according to an embodiment of the present invention. The method can be applied to the MG server, is used for tracking the calling path and the processing state in the asynchronous processing process of the message, and can apply manual intervention to the task with processing failure. Fig. 2 is an application scenario of the calling method shown in fig. 1 according to an embodiment of the present invention.
The specific flow chart of the calling method is described in detail below in conjunction with what is shown in fig. 1 and 2. As shown in fig. 1 and 2, the method may include the steps of:
step 110: a service invocation message is sent into the first message queue S1. The first message queue is a queue for storing service call messages sent from the respective different service systems 100.
Each service invocation message sent by the business system 100 carries an identification number for distinguishing between different service invocation messages. The identification number can be in any form or type of data, and can only play a role in distinguishing and authenticating the message, such as serial numbers which are arranged in time sequence.
That is, each service invocation message has a unique identification number from which the corresponding service invocation message can be determined.
Step 120: the service call message is fetched from the first message queue, converted into task data and stored in the database 200. The service invocation message temporarily stored in the first message queue may be consumed by the dispatch service 300, fetched from the first message queue and processed for conversion into task data.
These task data are stored in the database 200 and are awaiting processing. Each task data is marked with a processing state representing the processing of the task. When generating task data, the processing state is marked as an initial state, indicating that the task data is in a state of waiting for processing.
Step 130: and taking out the task data from the database, converting the task data into a message entity and sending the message entity to a second message queue.
The second message queue S2 is a message queue in the MQ server for temporarily storing message entities to be processed. In the present embodiment, the first message queue and the second message queue are used for naming in order to distinguish from the message queue in which the service call message is placed.
Specifically, the scheduling service 300 may take out the task data with the processing state being the initial state from the database according to a preset time period by means of a timing polling. The specific time period or timing time is an empirical value and can be set by those skilled in the art as desired in the actual situation.
Step 140: and retrieving the message entity from the second message queue and processing the message entity.
The message entity in the second message queue may be consumed by the application server 400 and processed accordingly, to implement a call to the service.
Step 150: and updating the processing state of the task data according to the processing result of the message entity.
Based on the processing result finally obtained after the application server 400 processes the message entity, the processing state of the task data can be correspondingly updated through the unique identification number.
In some embodiments, the updating of the processing state of the task data may also be implemented by using a form of message queue, and specifically may include the following steps:
first, the application server 400 transmits the processing state of the task data to the third message queue S3 according to the processing result. The task data processing status placed in the third message queue is also provided with the identification number, indicating which task data is specifically the current processing situation.
Then, by the identification number, the scheduling service 300 may search the database for matching task data and update the processing state of the matching task data.
During processing by the application server 400, message entities may experience processing failures due to various factors. In order to continue to complete the service call requirement of the service system, the task data in the failure state can be manually interfered, and the task data can be processed by manual operation or processing.
The manual intervention may specifically take any suitable form or manner, such as a retry, a retry after adjustment, or directly terminate the task data. In some embodiments, for task data in a failed state, a retry instruction may be issued by a technician manually to retry the task data.
In other embodiments, the technician may also issue retry instructions to retry execution of the task data after manually modifying and adjusting the task data.
After receiving the retry instruction input by the technician, the processing state of the task data is restored to the initial state, so that the task data can be re-executed in steps 120 to 150 to re-try to process the task data.
In the application service calling method provided by the embodiment of the invention, the identification number carried in the service calling message is kept unchanged in the processing process of converting the service calling message into the task data and the message entity, and is kept carried by the task data and the message entity all the time.
Thus, the calling process and specific processing state of the service call message in the MQ server can be tracked through the identification number. Moreover, the task data in the failure state can be manually interfered, so that the use requirement of a user is well met.
Fig. 3 is a schematic diagram of a change in processing status of a message according to an embodiment of the present application. In this embodiment, the processing states of the task data include: an initial state, a first processing state, a second processing state, a third processing state, and a failure state.
Wherein the initial state indicates that the task data is stored in the database awaiting processing. The first processing state indicates that the message entity has been processed successfully and informs the caller. The second processing state indicates that the message entity processing was successful but did not notify the caller. The third processing state indicates that the message entity processing was successful but there is a subsequent flow of processing, and the failure state indicates that the message entity processing was unsuccessful.
For the processed task data, corresponding processes can be executed according to different processing states of the task data. As shown in fig. 3, task data 310 in an initial state is periodically retrieved from the database and converted to a message entity in an executing state 320 in which processing is performed.
Depending on the processing results, the processing state may be updated to one of the first processing state, the second processing state, the third processing state, and the failure state.
When the processing state is the first processing state 330, it indicates that the processing procedure of the task data is completed. Therefore, it can be used as history data, and no further processing is performed.
When the processing state is the second processing state 340, task data thereof can be converted into a message entity according to a preset time period by a timing polling mode and sent to a fourth message queue. The task of notifying the caller is completed by scheduling the consumption of the message in the fourth message queue by the server.
Similar to the above embodiments, the fourth message queue may also decouple task data from the notification caller. Thus, after placement in the fourth message queue, the processing state of the task data may be updated to the first processing state 330.
When the processing state is the third processing state 350, the following multiple processing flows are continuously executed according to the requirement of the task data until the processing is completed.
When the processing state is the failure state 360, the task data may be updated to the initial state by manual operation after the data is modified or not modified to retry processing the task data.
Fig. 4 shows a schematic structural diagram of a calling device of an application service according to an embodiment of the present invention. As shown in fig. 4, the calling device of the application service may include: a business application module 410, a first dispatch service module 420, a second dispatch service module 430, an application service module 440, and a third dispatch service module 450.
The service application module 410 is configured to send a service call message to the first message queue, where the service call message carries an identification number for distinguishing different service call messages. The first dispatch service module 320 is configured to fetch the service call message from the first message queue, convert the service call message into task data, and store the task data in a database, where a processing state of the task data is marked as an initial state. The second dispatch service module 330 is configured to retrieve the task data from the database, convert the task data into a message entity, and send the message entity to a second message queue. The application service module 440 is configured to fetch and process the message entity from the second message queue. The third scheduling service module 450 is configured to update the processing state of the task data according to the processing result of the message entity.
By the application service calling device provided by the embodiment of the invention, the message header sent by the business system service carries the identification number which penetrates through the whole asynchronous message processing flow, and a specific calling path can be determined based on the identification number, and the execution state can be known. In addition, the message of processing failure can also be subjected to manual intervention operation (such as retry, termination or retry after modification), so that the method has good application prospect.
The embodiment of the invention provides a non-volatile computer storage medium, which stores at least one executable instruction, and the computer executable instruction can execute the calling method of the application service in any method embodiment.
The executable instructions may be particularly useful for causing a processor to: sending a service call message to a first message queue, wherein the service call message carries an identification number for distinguishing different service call messages; the service call message is taken out from the first message queue, converted into task data and stored in a database, and the processing state of the task data is marked as an initial state; the task data is taken out from the database, converted into a message entity and sent to a second message queue; retrieving and processing the message entity from the second message queue; and updating the processing state of the task data according to the processing result of the message entity.
Fig. 5 shows a schematic structural diagram of an embodiment of an electronic device according to an embodiment of the present invention, which is not limited to a specific implementation of the electronic device.
As shown in fig. 5, the electronic device may include: a processor 502, a communication interface (Communications Interface) 504, a memory 506, and a communication bus 508.
Wherein the processor 502, the communication interface 504, and the memory 506 communicate with each other via a communication bus 508. A communication interface 504 for communicating with network elements of other devices, such as clients or other servers. The processor 502 is configured to execute the program 510, and may specifically perform relevant steps in the above-mentioned method embodiment for calling an application service.
In particular, program 510 may include program code including computer-operating instructions.
The processor 502 may be a central processing unit CPU, or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in the electronic device may be the same type of processor, such as one or more CPUs; but may also be different types of processors such as one or more CPUs and one or more ASICs.
A memory 506 for storing a program 510. Memory 506 may comprise high-speed RAM memory or may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 510 may be specifically operable to cause the processor 502 to: sending a service call message to a first message queue, wherein the service call message carries an identification number for distinguishing different service call messages; the service call message is taken out from the first message queue, converted into task data and stored in a database, and the processing state of the task data is marked as an initial state; the task data is taken out from the database, converted into a message entity and sent to a second message queue; retrieving and processing the message entity from the second message queue; and updating the processing state of the task data according to the processing result of the message entity.
The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a construction of such a system is apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (8)
1. A method for invoking an application service, the method comprising:
sending a service call message to a first message queue, wherein the service call message carries an identification number for distinguishing different service call messages;
the service call message is taken out from the first message queue, converted into task data and stored in a database, and the processing state of the task data is marked as an initial state;
the task data is taken out from the database, converted into a message entity and sent to a second message queue;
retrieving and processing the message entity from the second message queue;
updating the processing state of the task data according to the processing result of the message entity;
according to the processing result, the processing state of the task data is sent to a third message queue;
searching matched task data in the database through the identification number and updating the processing state of the matched task data;
the processing state includes: a first processing state for indicating that the message entity processing is successful and notifying the caller, a second processing state for indicating that the message entity processing is successful but not notifying the caller, a third processing state for indicating that the message entity processing is successful but also a subsequent processing flow, and a failure state that the message entity processing is unsuccessful.
2. The method according to claim 1, wherein the method further comprises:
converting the task data with the processing state being the second processing state into a message entity according to a preset time period in a timing polling mode, and sending the message entity into a fourth message queue;
and updating the processing state of the task data into a first processing state.
3. The method according to claim 1, wherein after updating the processing state of the task data according to the processing result of the message entity, the method further comprises:
and after receiving the retry instruction, recovering the task data with the processing state of failure to an initial state.
4. The method according to claim 1, wherein task data whose processing state is an initial state is fetched from the database by means of a timer poll for a preset period of time.
5. The method of claim 1, wherein the identification number remains unchanged during the conversion of the service invocation message into task data and a message entity, both carrying the identification number.
6. An application service invocation apparatus, the apparatus comprising:
the service application module is used for sending service calling information to the first information queue, wherein the service calling information carries identification numbers for distinguishing different service calling information;
the first scheduling service module is used for taking out the service call message from the first message queue, converting the service call message into task data and storing the task data in a database, wherein the processing state of the task data is marked as an initial state;
the second scheduling service module is used for taking out the task data from the database, converting the task data into a message entity and sending the message entity into a second message queue;
the application service module is used for taking out the message entity from the second message queue and processing the message entity;
the third scheduling service module is used for updating the processing state of the task data according to the processing result of the message entity;
the state sending module is used for sending the processing state of the task data to a third message queue according to the processing result;
the first processing state module is used for searching matched task data in the database through the identification number and updating the processing state of the matched task data;
a second processing state module for the processing state comprising: a first processing state for indicating that the message entity processing is successful and notifying the caller, a second processing state for indicating that the message entity processing is successful but not notifying the caller, a third processing state for indicating that the message entity processing is successful but also a subsequent processing flow, and a failure state that the message entity processing is unsuccessful.
7. An electronic device comprising a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to perform the steps of the method for invoking an application service according to any of claims 1-5.
8. A non-volatile computer storage medium, characterized in that it has stored therein at least one computer program that causes a processor to execute the steps of the method for invoking application services according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911283987.1A CN111090532B (en) | 2019-12-13 | 2019-12-13 | Application service calling method, device, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911283987.1A CN111090532B (en) | 2019-12-13 | 2019-12-13 | Application service calling method, device, electronic equipment and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111090532A CN111090532A (en) | 2020-05-01 |
| CN111090532B true CN111090532B (en) | 2023-06-20 |
Family
ID=70395563
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911283987.1A Active CN111090532B (en) | 2019-12-13 | 2019-12-13 | Application service calling method, device, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111090532B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181737B (en) * | 2020-09-25 | 2024-08-13 | 中国建设银行股份有限公司 | Message processing method, device, electronic equipment and medium |
| CN114510326A (en) * | 2020-11-17 | 2022-05-17 | 湖南微步信息科技有限责任公司 | Task scheduling method and device, electronic equipment and storage medium |
| CN113220471A (en) * | 2021-04-13 | 2021-08-06 | 北京齐尔布莱特科技有限公司 | Data processing method and device, computing equipment and storage medium |
| CN114124871A (en) * | 2021-11-24 | 2022-03-01 | 中国银行股份有限公司 | Message information processing method and device of MQ message queue |
| CN117076096B (en) * | 2023-10-17 | 2024-12-31 | 腾讯科技（深圳）有限公司 | Task flow execution method and device, computer readable medium and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6529932B1 (en) * | 1998-04-01 | 2003-03-04 | Microsoft Corporation | Method and system for distributed transaction processing with asynchronous message delivery |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
-
2019
- 2019-12-13 CN CN201911283987.1A patent/CN111090532B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6529932B1 (en) * | 1998-04-01 | 2003-03-04 | Microsoft Corporation | Method and system for distributed transaction processing with asynchronous message delivery |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111090532A (en) | 2020-05-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111090532B (en) | Application service calling method, device, electronic equipment and computer storage medium | |
| CN108536532B (en) | Batch task processing method and system | |
| CN112099935B (en) | Task processing method and device | |
| JP6336988B2 (en) | System and method for small batch processing of usage requests | |
| CN108965457A (en) | A kind of message delivery method of distributed cluster system, device, equipment and medium | |
| CN106407021A (en) | Queue-based business request processing method | |
| CN106250250A (en) | Data communications method and device | |
| CN110750341A (en) | Task scheduling method, device, system, terminal device and storage medium | |
| CN103562890A (en) | Managing message subscription in publish/subscribe messaging system | |
| CN112667382A (en) | Task scheduling method, device, equipment and storage medium | |
| CN104579905A (en) | Message passing method and system, MOM (message oriented middleware) server and receiving terminal | |
| JP2005521945A (en) | Optimal server in common work queue environment | |
| CN108259595A (en) | The method and system of asynchronous call between a kind of service | |
| CN108900627B (en) | Network request method, terminal device and storage medium | |
| US10929237B2 (en) | Error handling tool | |
| CN115964153A (en) | Asynchronous task processing method, device, equipment and storage medium | |
| CN119440879A (en) | Message processing method, device, equipment and storage medium | |
| CN110008187B (en) | File transmission scheduling method, device, equipment and computer readable storage medium | |
| CN115333942A (en) | Event retry method and device, storage medium and electronic equipment | |
| CN107819855A (en) | A kind of message distributing method and device | |
| CN117762652A (en) | Distributed transaction processing method and device based on message middleware | |
| CN114615284B (en) | In-cluster message notification method, receiving method and device | |
| US8869171B2 (en) | Low-latency communications | |
| CN112783613B (en) | Method and device for scheduling units | |
| US10419368B1 (en) | Dynamic scaling of computing message architecture |
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 | ||
| GR01 | Patent grant |