CN112437000A - Message queue pushing method and device, computer equipment and storage medium - Google Patents
Message queue pushing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112437000A CN112437000A CN202011279375.8A CN202011279375A CN112437000A CN 112437000 A CN112437000 A CN 112437000A CN 202011279375 A CN202011279375 A CN 202011279375A CN 112437000 A CN112437000 A CN 112437000A
- Authority
- CN
- China
- Prior art keywords
- message
- receiving
- rule
- producer
- pushing
- 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
- 238000000034 method Methods 0.000 title claims abstract description 68
- 230000008569 process Effects 0.000 claims abstract description 31
- 238000012790 confirmation Methods 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 abstract description 6
- 238000005457 optimization Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 239000000306 component Substances 0.000 description 2
- 239000008358 core component Substances 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 239000003999 initiator Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- 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
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- 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/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the field of data transmission optimization, and discloses a message queue pushing method, a message queue pushing device, a computer device and a storage medium, wherein the message queue pushing method comprises the following steps: acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data; searching a sending rule of a message producer; determining a message receiving object according to a sending rule; acquiring a receiving rule of a message receiving object; and pushing the message to the message receiving object according to the receiving rule so that the message receiving object processes the business process associated with the financial business data. The invention solves the problems of high updating difficulty and high updating cost when the message queue framework is updated, and simultaneously supports the personalized setting of message sending and receiving, and improves the message pushing accuracy.
Description
Technical Field
The present invention relates to the field of data transmission optimization, and in particular, to a message queue pushing method, an apparatus, a computer device, and a storage medium.
Background
Message queue services have become an important means of application system communication, have functions of low coupling, reliable delivery, broadcasting, flow control, final consistency, and the like, and can be used for asynchronous remote procedure calls. The message queue service has two important roles, a message producer and a message consumer. Message queue services require the integration of message producers and message consumers within the same message queue framework. This requires that each application (message consumer) using the message queue service needs an inline message queue framework.
As the message queue frame is iteratively updated, the message queue frame of the application system is also updated. However, different application systems have differences, and therefore, special debugging is required in the updating process of the message queue framework, which increases the difficulty and cost of updating. Also, messages are susceptible to loss during updates.
Disclosure of Invention
Therefore, it is necessary to provide a message queue pushing method, a message queue pushing device, a computer device, and a storage medium for solving the problems of high update difficulty and high update cost when updating a message queue framework.
A message queue pushing method, comprising:
acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
searching a sending rule of the message producer;
determining a message receiving object according to the sending rule;
acquiring a receiving rule of the message receiving object;
and pushing the message to the message receiving object according to the receiving rule so as to enable the message receiving object to process the business process associated with the financial business data.
A message queue pushing device, comprising:
the message consumption module is used for acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
the searching and sending rule module is used for searching the sending rule of the message producer;
a receiving object determining module, configured to determine a message receiving object according to the sending rule;
the receiving rule obtaining module is used for obtaining the receiving rule of the message receiving object;
and the message pushing module is used for pushing the message to the message receiving object according to the receiving rule so as to enable the message receiving object to process the business process associated with the financial business data.
A computer device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor implementing the message queue pushing method when executing the computer readable instructions.
One or more readable storage media storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform a message queue pushing method as described above.
According to the message queue pushing method, the message queue pushing device, the computer equipment and the storage medium, the message generated by the message producer is obtained from the message queue server according to the preset obtaining frequency, the message comprises financial business data, and the message on the message queue server is consumed through the MQ service platform. And searching the sending rule of the message producer to determine the sending mode (including receiving objects, time, importance and the like) of the message according to the sending rule predefined by the message producer. And determining a message receiving object according to the sending rule so as to determine an actual consumption object of the message. And acquiring a receiving rule of the message receiving object to determine a message receiving mode according to the receiving rule predefined by the message receiving object (application system). And pushing the message to the message receiving object according to the receiving rule so that the message receiving object processes the business process associated with the financial business data to complete the pushing of the message and complete the business process related to the message. The message queue pushing method provided by the invention completely decouples the contact between the message receiving object and the message queue framework, consumes the information through the MQ service platform and ensures that the message can be pushed to the message receiving object. The invention solves the problems of high updating difficulty and high updating cost when the message queue framework is updated, and simultaneously supports the personalized setting of message sending and receiving, and improves the message pushing accuracy.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a diagram of an application environment of a message queue pushing method according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a message queue pushing method according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a message queue pushing apparatus according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The message queue pushing method provided by this embodiment can be applied to the application environment shown in fig. 1, in which a client communicates with a server. The client includes, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of a plurality of servers.
In an embodiment, as shown in fig. 2, a message queue pushing method is provided, which is described by taking the application of the method to the server side in fig. 1 as an example, and includes the following steps:
and S10, acquiring the message generated by the message producer from the message queue server according to the preset acquisition frequency, wherein the message comprises financial service data.
The message queue pushing method provided by this embodiment may be implemented by an MQ service platform (message queue service platform) disposed at a service end. The message queue server is a core component of the message queue service and provides the core service for the message queue. The message producer is the producer of the message, the initiator of the service, and is responsible for producing the message and transmitting the message to the message queue server. At this point, the MQ service platform obtains from the message queue server the messages that the message producer generated and had uploaded to the message queue server. The MQ service platform is a message consumer of the message queue service, but the MQ service platform only serves as a transfer party of the message and is not an ultimate consumer of the message, namely a processing party of the business. The preset acquisition frequency may be set based on the generation characteristics of the message producer. For example, the message producer may generate 1000 pieces per hour for the first time period, the message queue may have 50 pieces per hour for the second time period, the acquisition frequency of the MQ service platform may be set to the first acquisition frequency, e.g., 30s, for the first time period, and the acquisition frequency may be set to the second acquisition frequency, e.g., 90s, for the second time period. That is, the first acquisition frequency is greater than the second acquisition frequency. The message producer may be a task distribution center of a financial group, and thus, typically, the message produced by the message producer includes financial transaction data. In one example, the message producer is a registered message source, i.e., the message producer needs to be pre-registered with the MQ service platform.
S20, searching the sending rule of the message producer.
The sending rule is a sending rule that a message producer uploads to the MQ service platform in advance. Thus, the sending rules are asynchronous to the pushing of messages. The sending rules may define that messages of different content are pushed to different application systems. For example, if the message belongs to type a, the message is pushed to an application system associated with type a; and if the message belongs to the type B, pushing the message to an application system associated with the type B. The message type may be defined based on actual needs. Similarly, the association relationship between the message type and the application system can be set in advance according to actual needs. In some cases, the transmission rule further includes a transmission time, a transmission importance, and the like. Specifically, the MQ service platform only sends messages to the message receiving object at the sending time. The sending importance can customize some important fields, and if the message contains the important fields defined in the sending importance, the sending importance of the message is high. And sending the message with high importance degree and having high priority in message pushing.
And S30, determining a message receiving object according to the sending rule.
Understandably, the message reception object may be determined according to the reception object defined in the transmission rule. If the sending rule does not specifically limit the receiving object, all the application systems are the message receiving objects by default. Here, the message recipient object is the ultimate consumer of the message, which is the processing party of the service. In one example, the message recipient object is a registered message consumer, i.e., the message recipient object needs to be pre-registered with the MQ service platform.
S40, obtaining the receiving rule of the message receiving object.
Here, the reception rule is a reception rule in which a message reception object is uploaded to the MQ service platform in advance. The receiving rules include, but are not limited to, message subject (TOPIC), message retransmission rules, message failure rules. Specifically, the message retransmission rule may include whether retransmission is required, the number of retransmissions, the retransmission interval, and the like. Message failure rules include failure warnings, failure notifications, and the like. The receiving rules of different message receiving objects may be the same or different. The reception rule settings of the respective message reception objects are independent of each other.
S50, pushing the message to the message receiving object according to the receiving rule so as to enable the message receiving object to process the business process associated with the financial business data.
Understandably, the message may be pushed to the message receiving object according to the receiving rule so that the message receiving object receives the message. If the message receiving object can not receive the message, failure processing is carried out according to the receiving rule, for example, a message failure notice is returned to the message producer. Here, the MQ service platform may push the message to the message receiving object through a specific communication interface, such as may push the message to the message receiving object through an http (hypertext transfer protocol) service interface.
When the message queue framework is upgraded, at the customer end, only the framework of the MQ service platform needs to be directly upgraded, and all message receiving objects do not need to be correspondingly upgraded, so that the updating difficulty and the updating cost are greatly reduced, and the problems of high updating difficulty and high updating cost when the message queue framework is updated are solved. Meanwhile, the method provided by the embodiment also releases the coupling between the application system (message receiving object) and the message queue frame, the application system does not need to pay attention to what type of message is transmitted, and does not need to manage the influence caused by upgrading or other changes of the message queue frame, and only needs to provide an http service interface, so that the maintenance of the application system is greatly simplified, and meanwhile, the application system is lighter.
In one example, a message producer may be a task distribution center of a financial group, and a message recipient may refer to a plurality of business subsystems administered by the financial group. And the task message issued by the task issuing center is pushed to the service subsystem through the message queue server and the MQ service platform. When the framework of the message queue server is upgraded, only the task issuing center and the MQ service platform need to be upgraded synchronously, and the service subsystem can still normally receive the task message issued by the task issuing center without upgrading.
After the message receiving object receives the message, the financial business data contained in the message is automatically identified, and then the business process associated with the financial business data is automatically triggered. For example, if the financial transaction data is account checking information, the transaction flow associated with the account checking information is bill verification and accounting flow.
In steps S10-S50, the message generated by the message producer is acquired from the message queue server according to the preset acquisition frequency, the message includes financial service data, so as to consume the message on the message queue server through the MQ service platform. And searching the sending rule of the message producer to determine the sending mode (including receiving objects, time, importance and the like) of the message according to the sending rule predefined by the message producer. And determining a message receiving object according to the sending rule so as to determine an actual consumption object of the message. And acquiring a receiving rule of the message receiving object to determine a message receiving mode according to the receiving rule predefined by the message receiving object (application system). And pushing the message to the message receiving object according to the receiving rule so that the message receiving object processes the business process associated with the financial business data to finish the pushing of the message. The message queue pushing method provided by the embodiment completely decouples the contact between the message receiving object and the message queue frame, consumes information through the MQ service platform, ensures that the message can be pushed to the message receiving object, and meanwhile, the message producer does not need to ensure the retransmission of the message, thereby solving the problems of high updating difficulty and high updating cost when the message queue frame is updated, and simultaneously, supporting the personalized setting of message sending and receiving, and improving the message pushing accuracy.
Optionally, step S10, before the obtaining the message generated by the message producer from the message queue server according to the preset obtaining frequency, further includes:
s11, the message producer generates the message according to a preset generation rule;
and S12, the message producer sends the message to the message queue server.
Understandably, the preset generation rule can be set according to actual needs. In one example, the message producer may be a task management center for producing messages containing business tasks. And the message queue server, which serves as a core component of the message queue service, can receive a plurality of messages from the message producer to form a message queue for consumption by a message consumer (here, the message consumer is uniquely designated as an MQ service platform).
In steps S11-S12, the message producer generates the message according to a preset generation rule, where the message producer is the source of the message. And the message producer sends the message to the message queue server so as to add the message into a message queue.
Optionally, in step S10, after the step of obtaining the message generated by the message producer from the message queue server according to the preset obtaining frequency, the method further includes:
s13, the message queue server generates the consumption result of the message;
and S14, the message queue server returns the consumption result to the message producer.
Understandably, after the MQ service platform obtains the message from the message queue server, the message queue server generates a consumption result for the message, i.e., indicating that the message has been consumed. At the same time, the message queue of the message queue server no longer stores the message.
The message queue server returns the consumption result to the message producer. The message producer can process the subsequent business according to the consumption result. Generally, the response time of the MQ service platform is much shorter than that of the application system. Thus, the message producer can receive the consumption result in a shorter time, which can greatly improve the processing efficiency of the message producer.
In steps S13-S14, the message queue server generates a consumption result of the message to determine that the message has been consumed by the MQ service platform. And the message queue server returns the consumption result to the message producer so that the message producer knows that the message is consumed.
Optionally, step S20, before the searching for the sending rule of the message producer, further includes:
s21, receiving a first registration request sent by the message producer;
s22, registering the message producer according to the first registration request, and receiving the sending rule sent by the message producer after the registration is successful;
and S23, storing the sending rule in a first storage position.
In this embodiment, the MQ service platform is provided with a registration component, and can accept registration of the message producer. After registration is complete, the sending rule may be received from the message producer and stored in the first storage location. The first storage location may be a storage location set according to actual needs, such as a certain data table in a rule database. Here, the security of the message source is ensured by means of registering the message producer.
In steps S21-S23, a first registration request sent by the message producer is received to ensure the validity of the message producer. And registering the message producer according to the first registration request, and receiving the sending rule sent by the message producer after the registration is successful so as to obtain the sending rule for determining the message sending mode. And storing the sending rule in a first storage position to finish the storage of the sending rule.
Optionally, in step S40, before the obtaining the receiving rule of the message receiving object, the method further includes:
s41, receiving a second registration request sent by the message receiving object;
s42, registering the message receiving object according to the second registration request, and receiving the receiving rule sent by the message producer after the registration is successful;
and S43, storing the receiving rule in a second storage position.
In this embodiment, the registration component provided by the MQ service platform may also accept registration of message receiving objects (i.e., application systems). After the registration is completed, the receiving rule may be obtained from the message receiving object and stored in the second storage location. The second storage location may be a storage location set according to actual needs, such as a certain data table in a rule database. Here, security of message usage (consumption) is ensured by registering a message reception object.
In steps S41-S43, a second registration request sent by the message receiving object is received to ensure the validity of the message receiving object. And registering the message receiving object according to the second registration request, and receiving the receiving rule sent by the message producer after the registration is successful so as to obtain the receiving rule for determining the message receiving mode. And storing the receiving rule in a second storage position to finish the storage of the receiving rule.
Optionally, step S50, that is, the pushing the message to the message receiving object according to the receiving rule includes:
s501, judging whether the message is matched with the message theme in the receiving rule or not;
s502, if the message is matched with the message subject in the receiving rule, the message is pushed to the message receiving object.
Understandably, the reception rules include, but are not limited to, message subject (TOPIC), message retransmission rules, message failure rules. Specifically, the message retransmission rule may include whether retransmission is required, the number of retransmissions, the retransmission interval, and the like. Message failure rules include failure warnings, failure notifications, and the like.
The message receiving object may set the message subject at the receiving rule. And when the message is matched with the message subject, pushing the message to a message receiving object. For example, if the message topic subscribed by the message receiving object X is "securities", the message topic "securities" is written into the receiving rule and sent to the MQ service platform; when the MQ service platform receives the message with the message topic of 'securities', and the message receiving object X has the authority of acquiring the message, the MQ service platform pushes the message to the message receiving object X.
In steps S501-S502, it is determined whether the message is matched with the message topic in the receiving rule, so as to improve the accuracy of message pushing in a message topic matching manner. If the message is matched with the message theme in the receiving rule, the message is pushed to the message receiving object so as to complete the pushing of the message matched with the message theme.
Optionally, step S50, that is, the pushing the message to the message receiving object according to the receiving rule includes:
s503, after the message is pushed to the message receiving object, if the confirmation information returned by the message receiving object is not received, the message is pushed to the message receiving object according to the retransmission rule in the receiving rule;
s504, when the pushing times of the message is larger than the upper limit times set by the receiving rule, generating a pushing failure notice, and sending the pushing failure notice to the message producer.
Understandably, the MQ service platform pushes the message to the message receiving object according to the receiving rule, if the acknowledgement information returned by the message receiving object is not received, the pushing is indicated to be failed, and at this time, the message needs to be continuously pushed to the message receiving object according to the retransmission rule in the receiving rule. The retransmission rules define whether retransmission is required, the number of retransmissions, and the repetition interval. If receiving the confirmation information returned by the message receiving object, the message receiving object indicates that the pushing is successful, and at the moment, the message receiving object consumes the received message and processes the corresponding service task.
And when the push times of the message are greater than the upper limit times (namely the retransmission times) set by the receiving rule, generating a push failure notice according to the message failure rule, and sending the push failure notice to the message producer.
In steps S503-S504, after the message is pushed to the message receiving object, if the confirmation information returned by the message receiving object is not received, the message is pushed to the message receiving object according to the retransmission rule in the receiving rule, so as to implement retransmission of the message. And when the pushing times of the message are larger than the upper limit times set by the receiving rule, generating a pushing failure notice, and sending the pushing failure notice to the message producer to determine that the message is failed to be pushed.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In an embodiment, a message queue pushing device is provided, where the message queue pushing device corresponds to the message queue pushing method in the foregoing embodiments one to one. As shown in fig. 3, the message queue pushing device includes a message consumption module 10, a search sending rule module 20, a receive object determining module 30, a receive rule acquiring module 40, and a message pushing module 50. The functional modules are explained in detail as follows:
a message consumption module 10, configured to acquire, from a message queue server, a message generated by a message producer according to a preset acquisition frequency, where the message includes financial service data;
a search sending rule module 20, configured to search a sending rule of the message producer;
a receive object determining module 30, configured to determine a message receive object according to the sending rule;
an obtaining receiving rule module 40, configured to obtain a receiving rule of the message receiving object;
a message pushing module 50, configured to push the message to the message receiving object according to the receiving rule, so that the message receiving object processes a business process associated with financial business data.
Optionally, the message queue pushing apparatus further includes:
the message generating module is used for generating the message according to a preset generating rule by the message producer;
and the message uploading module is used for sending the message to the message queue server by the message producer.
Optionally, the message queue pushing apparatus further includes:
a consumption result generation module for generating the consumption result of the message by the message queue server;
and the consumption result returning module is used for returning the consumption result to the message producer by the message queue server.
Optionally, the module 20 for searching and sending rules further includes:
a first registration request receiving unit, configured to receive a first registration request sent by the message producer;
a receiving and sending rule unit, configured to register the message producer according to the first registration request, and receive the sending rule sent by the message producer after the registration is successful;
a first storage unit, configured to store the sending rule in a first storage location.
Optionally, the obtaining receiving rule module 40 further includes:
a second registration request receiving unit, configured to receive a second registration request sent by the message receiving object;
a receiving rule unit, configured to register the message receiving object according to the second registration request, and receive the receiving rule sent by the message producer after the registration is successful;
a second storage unit, configured to store the receiving rule in a second storage location.
Optionally, the message pushing module 50 includes:
the theme matching unit is used for judging whether the message is matched with the message theme in the receiving rule or not;
and the message pushing unit is used for pushing the message to the message receiving object if the message is matched with the message theme in the receiving rule.
Optionally, the message pushing module 50 includes:
a retransmission unit, configured to, after pushing the message to the message receiving object, if acknowledgement information returned by the message receiving object is not received, push the message to the message receiving object according to a retransmission rule in the receiving rule;
and the pushing failure unit is used for generating a pushing failure notice when the pushing times of the message are greater than the upper limit times set by the receiving rule and sending the pushing failure notice to the message producer.
For specific definition of the message queue pushing device, refer to the above definition of the message queue pushing method, which is not described herein again. The modules in the message queue pushing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 4. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a readable storage medium and an internal memory. The readable storage medium stores an operating system, computer readable instructions, and a database. The internal memory provides an environment for the operating system and execution of computer-readable instructions in the readable storage medium. The database of the computer device is used for storing data related to the message queue pushing method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer readable instructions, when executed by a processor, implement a message queue pushing method. The readable storage media provided by the present embodiment include nonvolatile readable storage media and volatile readable storage media.
In one embodiment, a computer device is provided, comprising a memory, a processor, and computer readable instructions stored on the memory and executable on the processor, the processor when executing the computer readable instructions implementing the steps of:
acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
searching a sending rule of the message producer;
determining a message receiving object according to the sending rule;
acquiring a receiving rule of the message receiving object;
and pushing the message to the message receiving object according to the receiving rule so that the message receiving object processes the business process associated with the financial business data.
In one embodiment, one or more computer-readable storage media storing computer-readable instructions are provided, the readable storage media provided by the embodiments including non-volatile readable storage media and volatile readable storage media. The readable storage medium has stored thereon computer readable instructions which, when executed by one or more processors, perform the steps of:
acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
searching a sending rule of the message producer;
determining a message receiving object according to the sending rule;
acquiring a receiving rule of the message receiving object;
and pushing the message to the message receiving object according to the receiving rule so that the message receiving object processes the business process associated with the financial business data.
It will be understood by those of ordinary skill in the art that all or part of the processes of the methods of the above embodiments may be implemented by hardware related to computer readable instructions, which may be stored in a non-volatile readable storage medium or a volatile readable storage medium, and when executed, the computer readable instructions may include processes of the above embodiments of the methods. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A message queue pushing method, comprising:
acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
searching a sending rule of the message producer;
determining a message receiving object according to the sending rule;
acquiring a receiving rule of the message receiving object;
and pushing the message to the message receiving object according to the receiving rule so as to enable the message receiving object to process the business process associated with the financial business data.
2. The message queue pushing method according to claim 1, wherein before acquiring the message generated by the message producer from the message queue server according to the preset acquisition frequency, further comprising:
the message producer generates the message according to a preset generation rule;
the message producer sends the message to the message queue server.
3. The message queue pushing method according to claim 1, further comprising, after acquiring the message generated by the message producer from the message queue server:
the message queue server generates a consumption result of the message;
and the message queue server returns the consumption result to the message producer.
4. The message queue pushing method of claim 1, wherein before searching for the sending rule of the message producer, further comprising:
receiving a first registration request sent by the message producer;
registering the message producer according to the first registration request, and receiving the sending rule sent by the message producer after the registration is successful;
storing the sending rule in a first storage location.
5. The message queue pushing method according to claim 1, wherein before the obtaining the receiving rule of the message receiving object, further comprising:
receiving a second registration request sent by the message receiving object;
registering the message receiving object according to the second registration request, and receiving the receiving rule sent by the message producer after the registration is successful;
storing the receiving rule in a second storage location.
6. The message queue pushing method of claim 1, wherein the pushing the message to the message receiving object according to the receiving rule comprises:
judging whether the message is matched with the message subject in the receiving rule or not;
and if the message is matched with the message subject in the receiving rule, pushing the message to the message receiving object.
7. The message queue pushing method of claim 1, wherein the pushing the message to the message receiving object according to the receiving rule comprises:
after the message is pushed to the message receiving object, if the confirmation information returned by the message receiving object is not received, the message is pushed to the message receiving object according to the retransmission rule in the receiving rule;
and when the pushing times of the message are larger than the upper limit times set by the receiving rule, generating a pushing failure notice, and sending the pushing failure notice to the message producer.
8. A message queue pushing device, comprising:
the message consumption module is used for acquiring a message generated by a message producer from a message queue server according to a preset acquisition frequency, wherein the message comprises financial service data;
the searching and sending rule module is used for searching the sending rule of the message producer;
a receiving object determining module, configured to determine a message receiving object according to the sending rule;
the receiving rule obtaining module is used for obtaining the receiving rule of the message receiving object;
and the message pushing module is used for pushing the message to the message receiving object according to the receiving rule so as to enable the message receiving object to process the business process associated with the financial business data.
9. A computer device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein the processor when executing the computer readable instructions implements the message queue pushing method of any of claims 1 to 7.
10. One or more readable storage media storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the message queue pushing method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011279375.8A CN112437000A (en) | 2020-11-16 | 2020-11-16 | Message queue pushing method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011279375.8A CN112437000A (en) | 2020-11-16 | 2020-11-16 | Message queue pushing method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112437000A true CN112437000A (en) | 2021-03-02 |
Family
ID=74700642
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011279375.8A Pending CN112437000A (en) | 2020-11-16 | 2020-11-16 | Message queue pushing method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112437000A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113839987A (en) * | 2021-08-24 | 2021-12-24 | 广州市瑞立德信息系统有限公司 | Message queue-based message distribution method, access control system and storage medium |
| CN114253807A (en) * | 2021-12-20 | 2022-03-29 | 深圳前海微众银行股份有限公司 | Alarm information notification method and device |
| CN114374737A (en) * | 2022-01-12 | 2022-04-19 | 平安普惠企业管理有限公司 | Message pushing method and device, computer equipment and storage medium |
| CN114979256A (en) * | 2022-05-19 | 2022-08-30 | 北京京东乾石科技有限公司 | Message pushing method and device, electronic equipment and computer readable medium |
| CN116233053A (en) * | 2022-12-05 | 2023-06-06 | 中国联合网络通信集团有限公司 | Method, device and storage medium for sending service request message |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327039A (en) * | 2012-03-20 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and device and system for pushing messages |
| CN104253741A (en) * | 2014-07-31 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Information sending method and device and system thereof |
| US20180067983A1 (en) * | 2016-09-06 | 2018-03-08 | Kabushiki Kaisha Toshiba | System, client device, server device, and program |
| CN107911487A (en) * | 2017-12-18 | 2018-04-13 | 广东欧珀移动通信有限公司 | Information-pushing method, device, server and readable storage medium storing program for executing |
| US20180160396A1 (en) * | 2016-12-06 | 2018-06-07 | Guangzhou Ucweb Computer Technology Co., Ltd. | Message pushing method, client, server and programmable device |
-
2020
- 2020-11-16 CN CN202011279375.8A patent/CN112437000A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327039A (en) * | 2012-03-20 | 2013-09-25 | 腾讯科技（深圳）有限公司 | Method and device and system for pushing messages |
| CN104253741A (en) * | 2014-07-31 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Information sending method and device and system thereof |
| US20180067983A1 (en) * | 2016-09-06 | 2018-03-08 | Kabushiki Kaisha Toshiba | System, client device, server device, and program |
| US20180160396A1 (en) * | 2016-12-06 | 2018-06-07 | Guangzhou Ucweb Computer Technology Co., Ltd. | Message pushing method, client, server and programmable device |
| CN107911487A (en) * | 2017-12-18 | 2018-04-13 | 广东欧珀移动通信有限公司 | Information-pushing method, device, server and readable storage medium storing program for executing |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113839987A (en) * | 2021-08-24 | 2021-12-24 | 广州市瑞立德信息系统有限公司 | Message queue-based message distribution method, access control system and storage medium |
| CN113839987B (en) * | 2021-08-24 | 2024-04-30 | 广州市瑞立德信息系统有限公司 | Message distribution method based on message queue, access control system and storage medium |
| CN114253807A (en) * | 2021-12-20 | 2022-03-29 | 深圳前海微众银行股份有限公司 | Alarm information notification method and device |
| CN114374737A (en) * | 2022-01-12 | 2022-04-19 | 平安普惠企业管理有限公司 | Message pushing method and device, computer equipment and storage medium |
| CN114979256A (en) * | 2022-05-19 | 2022-08-30 | 北京京东乾石科技有限公司 | Message pushing method and device, electronic equipment and computer readable medium |
| CN116233053A (en) * | 2022-12-05 | 2023-06-06 | 中国联合网络通信集团有限公司 | Method, device and storage medium for sending service request message |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112437000A (en) | Message queue pushing method and device, computer equipment and storage medium | |
| US20140156785A1 (en) | Method and Apparatus for Generating User Notifications | |
| WO2020258666A1 (en) | Distributed system and data processing method | |
| WO2023207146A1 (en) | Service simulation method and apparatus for esop system, and device and storage medium | |
| CN112907344A (en) | Accounting data processing method and device, electronic equipment and storage medium | |
| CN112187453A (en) | Digital certificate updating method and system, electronic equipment and readable storage medium | |
| CN110223179B (en) | Data processing method, device, system and medium for fund | |
| CN114003659A (en) | Data synchronization method, data synchronization device, electronic equipment, storage medium and program product | |
| CN112559646A (en) | Report downloading method and device | |
| CN111930624A (en) | Test link message data processing method and device | |
| CN115098528B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN111178568A (en) | Service reservation request processing method, device, server and storage medium | |
| CN116414628A (en) | Transaction request processing method and device in new and old system switching process | |
| CN112182400B (en) | Message processing method, message processing device, electronic equipment and storage medium | |
| CN114004701A (en) | Method and device for generating transaction result, electronic equipment and storage medium | |
| CN112995932A (en) | Short message link monitoring method, device, equipment and medium based on Hash algorithm | |
| CN110738470B (en) | Electronic bill processing method, electronic bill processing device, storage medium and electronic bill processing equipment | |
| CN113486116A (en) | Data synchronization method and device, electronic equipment and computer readable medium | |
| CN111552907A (en) | Message processing method, device, equipment and storage medium | |
| US11941634B2 (en) | Systems and methods for a data connector integration framework | |
| CN113438227B (en) | Method, device, equipment and storage medium for limiting repeated request | |
| CN115170042A (en) | Graphic code management method, device, system, computing equipment and storage medium | |
| CN114493731A (en) | Merchant information processing system, method and medium | |
| CN113420019A (en) | Service data processing method and device | |
| CN114240649A (en) | Fee deduction method, fee deduction device, computer equipment, storage medium and program product |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20210302 |