Message subscription method and device based on unified message subscription platform, medium and equipment

Abstract

The invention relates to a message subscription method and device based on a unified message subscription platform, a medium and equipment. The method comprises the following steps: S1, when a unified message subscription platform receives a subscription registration request of a micro-service, binding a WebHook interface of the micro-service with a preset target theme and registering the WebHook interface and the preset target theme in the unified message subscription platform to realize persistence. And S2, when the unified message subscription platform subscribes to subscription data of a preset target theme, initiating a data push POST request to a WebHook interface corresponding to the preset target theme so as to transmit the subscription data to the micro-service. And S3, the micro service pushes a POST request based on the data received by the WebHook interface of the micro service, and executes the service logic corresponding to the subscription data. According to the method, real-time message subscription can be realized under the condition that a specific message middleware client SDK is not introduced into the micro-service, the expandability and adaptability of the system are improved, the problems of message middleware version sensitivity and code modification during switching can be effectively solved, and coupling of the micro-service and the message middleware is reduced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a message subscription method, device, medium and equipment based on a unified message subscription platform. Background Art

[0002] In the current microservice architecture, implementing real-time message subscription usually requires microservices to integrate a specific message middleware client SDK. However, this integration method is highly sensitive to the version of the message middleware, and a large amount of code needs to be modified when switching between different message middleware, which increases the complexity and maintenance cost of the system, resulting in a high degree of coupling between microservices and limiting the flexibility and scalability of the system. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide a message subscription method, device, medium and equipment based on a unified message subscription platform in view of the above-mentioned defects.

[0004] The technical solution adopted by the present invention to solve the technical problem is: a message subscription method based on a unified message subscription platform, each microservice is provided with a WebHook interface, comprising the following steps:

[0005] S1. When the unified message subscription platform receives a subscription registration request from a microservice, the WebHook interface of the microservice is bound to a preset target topic and registered in the unified message subscription platform to achieve persistence;

[0006] S2. When the unified message subscription platform subscribes to the subscription data of the preset target topic, it initiates a data push POST request to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice;

[0007] S3. The microservice pushes the POST request based on the data received by its WebHook interface and executes the business logic corresponding to the subscription data.

[0008] Furthermore, in the message subscription method of the present invention, before the unified message subscription platform receives the subscription registration request of the microservice, the method further includes:

[0009] Abstract multiple message subscription platforms to build a unified message subscription platform for publishing messages through a unified interface; one message subscription platform corresponds to one message middleware.

[0010] Further, in the message subscription method of the present invention, step S2 includes:

[0011] When the unified message subscription platform subscribes to the subscription data of the preset target topic, the subscription data is placed in the request body, and a data push POST request is initiated, so that the subscription data is transmitted together with the data push POST request to the WebHook interface of the corresponding microservice.

[0012] Further, in the message subscription method of the present invention, step S3 also includes:

[0013] When the microservice receives the data push POST request based on its WebHook interface, it responds within a preset time period, and after completing the response, executes the business logic corresponding to the subscription data.

[0014] Furthermore, in the message subscription method described in the present invention, the preset duration is less than 3 seconds.

[0015] Further, in the message subscription method of the present invention, the step of responding within a preset time period includes:

[0016] The microservice sends a response result containing an HTTPStatus status code to the unified message subscription platform within a preset time period; the HTTPStatus status code is used to identify whether the request is successful.

[0017] Furthermore, in the message subscription method described in the present invention, when the HTTPStatus status code is 200, it indicates that the data push POST request is successful.

[0018] In addition, the present invention also provides a message subscription device based on a unified message subscription platform, including at least one microservice and a unified message subscription platform, each microservice is provided with a WebHook interface, wherein:

[0019] The unified messaging subscription platform is used for:

[0020] When receiving a subscription registration request of a microservice, the WebHook interface of the microservice is bound to a preset target topic and registered in the unified message subscription platform to achieve persistence;

[0021] When subscribing to the subscription data of the preset target topic, a data push POST request is initiated to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice;

[0022] The microservice is used to: execute the business logic corresponding to the subscription data based on the data push POST request received by its WebHook interface.

[0023] In addition, the present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program is suitable for being loaded by a processor to execute the steps of the message subscription method based on the unified message subscription platform as described above.

[0024] In addition, the present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the steps of the message subscription method based on the unified message subscription platform as described above by calling the computer program stored in the memory.

[0025] The message subscription method, device, medium and equipment based on the unified message subscription platform of the present invention have the following beneficial effects: the present invention does not need to integrate a specific message middleware client SDK, and can realize real-time message subscription without introducing a specific message middleware client SDK into the microservice, thereby improving the scalability and adaptability of the system, and can effectively solve the problem of message middleware version sensitivity and code modification during switching, thereby reducing the cost of system integration and maintenance, reducing the coupling between microservices and message middleware, and improving the flexibility and maintainability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0027] Figure 1 It is a flow chart of a message subscription method based on a unified message subscription platform provided by an embodiment of the present invention;

[0028] Figure 2 It is a structural schematic diagram of a message subscription device based on a unified message subscription platform provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, the specific implementation methods of the present invention are now described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed", "set" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral body; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. When an element is referred to as being "on" or "under" another element, the element can be "directly" or "indirectly" located on the other element, or there may be one or more intermediate elements. The terms "first", "second", "third", etc. are only for the convenience of describing the present technical solution, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first", "second", "third", etc. can explicitly or implicitly include one or more of the features. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0030] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present invention. However, it should be clear to those skilled in the art that the present invention may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present invention.

[0031] In a preferred embodiment, in the message subscription method based on the unified message subscription platform of this embodiment, each microservice is provided with a WebHook interface. That is, each microservice is preset with a WebHook interface. It can be understood that the Webhook interface is a communication mechanism based on HTTP callback, which allows the application to automatically notify other services when a specific event occurs, that is, it is usually used to monitor certain behavioral events, and when the event is triggered, it will send information to the target address (URL) specified by the user. Each microservice is an application and can represent / contain a business.

[0032] refer to Figure 1, the method includes the following steps: S1. When the unified message subscription platform receives the subscription registration request of the microservice, it binds the WebHook interface of the microservice to the preset target topic and registers it in the unified message subscription platform to achieve persistence. S2. When the unified message subscription platform subscribes to the subscription data of the preset target topic, it initiates a data push POST request to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice. The subscription data is also the subscribed message. In other words, through interface registration, the unified message subscription platform will save the mapping relationship between the webhook interface and the topic (the preset target topic, that is, the specific topic), and obtain the other party's WebHook interface when receiving the subscription request of the microservice. The platform obtains the subscription message of the corresponding specific topic according to the WebHook interface and sends it to the microservice of the interface.

[0033] S3. The microservice pushes a POST request based on the data received by its WebHook interface and executes the business logic corresponding to the subscription data.

[0034] Compared with related technologies, each microservice needs to integrate, for example, a specific version of RabbitMQ. Then, when this RabbitMQ is replaced with Kafka or others, all microservices have to change the code (i.e., SDK) and reintegrate and re-connect to subscribe to messages. In this solution, each microservice no longer needs to integrate a specific message middleware client SDK, but instead implements message subscription by providing a WebHook interface and a unified message subscription platform. That is, real-time message subscription can be implemented without introducing a specific message middleware client SDK in the microservice, which improves the scalability and adaptability of the system, can effectively solve the version sensitivity of the message middleware and the code modification problem during switching, reduces the cost of system integration and maintenance, reduces the coupling between microservices and message middleware, and improves the flexibility and maintainability of the system.

[0035] In some embodiments, reference Figure 2 Before the unified message subscription platform receives the subscription registration request of the microservice, the method also includes: abstracting multiple message subscription platforms to build a unified message subscription platform for publishing messages through a unified interface. One message subscription platform corresponds to one message middleware, such as RabbitMQ, Kafka, Pulsar and other message subscription platforms of different types or versions. In other words, in order to smooth out various message subscription platforms (such as RabbitMQ, Kafka, Pulsar, etc.), the unified message subscription platform abstractly provides a unified interface for publishing messages, and the interface remains unchanged when the message platform is changed. Each microservice subscribes to the unified message subscription platform through the WebHook interface, instead of implementing message subscription through the client SDK of the integrated specific message middleware.

[0036] In this embodiment, each microservice is provided with a WebHook interface, and a unified message subscription platform that provides a unified interface for publishing messages is constructed by abstracting multiple message subscription platforms. When the unified message subscription platform receives a subscription registration request from a microservice, the WebHook interface of the microservice is bound to a preset target topic and registered in the unified message subscription platform to achieve persistence. When the unified message subscription platform subscribes to the subscription data of the preset target topic, a data push POST request is initiated to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice. The microservice executes the business logic corresponding to the subscription data based on the data push POST request received by its WebHook interface.

[0037] It can be understood that this embodiment introduces a unified message subscription platform to abstract various message platforms, such as RabbitMQ, Kafka, Pulsar, etc. Microservices no longer need to introduce a specific message middleware client SDK, but register with the unified message subscription platform by providing a WebHook interface, and transfer the work of integrating the message middleware client SDK to the unified message subscription platform. No matter how the message middleware is changed, the microservices will no longer be changed, so that the microservices can receive messages published by other services, and the purpose of real-time message subscription can be achieved without introducing a specific message middleware client SDK.

[0038] In some embodiments, step S2 includes: while the unified message subscription platform initiates a data push POST request, the subscription data is placed in the request body, so that the subscription data is transmitted to the WebHook interface of the corresponding microservice together with the data push POST request. That is to say, in this embodiment, each microservice is provided with a WebHook interface, and when the unified message subscription platform receives a subscription registration request from a microservice, the WebHook interface of the microservice is bound to the preset target topic and registered in the unified message subscription platform to achieve persistence. When the unified message subscription platform subscribes to the subscription data of the preset target topic, the subscription data is placed in the request body, and a data push POST request is initiated to the WebHook interface corresponding to the preset target topic, so that the subscription data is transmitted to the WebHook interface of the corresponding microservice together with the data push POST request. The microservice executes the business logic corresponding to the subscription data based on the data push POST request received by its WebHook interface.

[0039] This embodiment can reduce the coupling between microservices and message middleware, and improve the flexibility and maintainability of the system. It can solve the problem of message middleware version sensitivity and code modification during switching, and reduce the cost of system integration and maintenance. It enables microservices to implement real-time message subscription without introducing a specific message middleware client SDK, which improves the scalability and adaptability of the system. It enables the system to adapt to different message middleware platforms more flexibly, reducing the complexity of development and maintenance.

[0040] In some embodiments, step S3 further includes: when the microservice receives a data push POST request based on its WebHook interface, it responds within a preset time, and after completing the response, executes the business logic corresponding to the subscription data. That is, in this embodiment, each microservice is provided with a WebHook interface, and when the unified message subscription platform receives a subscription registration request of the microservice, the WebHook interface of the microservice is bound to the preset target topic and registered in the unified message subscription platform to achieve persistence. When the unified message subscription platform subscribes to the subscription data of the preset target topic, a data push POST request is initiated to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice. When the microservice receives a data push POST request based on its WebHook interface, it responds within a preset time, and after completing the response, executes the business logic or business volume logic corresponding to the subscription data. Optionally, the preset time is less than 3s. As an option, the microservice can send a response result containing an HTTPStatus status code to the unified message subscription platform within the preset time. The HTTPStatus status code is used to identify whether the request is successful. For example, when the HTTPStatus status code is 200, it means that the data push POST request is successful.

[0041] In a specific implementation, this method is used for the scenario where microservices subscribe to other service messages. First, the microservice develops the HTTP WebHook interface. This interface implements the business logic of subscribing to messages that was previously referenced or integrated with the message middleware client SDK. This logic is converted into a WebHook interface that provides a POST request method. In order to achieve efficient interface requests and prevent blocking, the interface timeout must be less than 3s. The interface does not have any response data. Whether the request is successful or not is marked by the HTTPStatus status code of the interface, 200 for success, and others for failure. After providing the interface, this WebHook interface and the Topic relationship that needs to be concerned are registered to the unified message subscription platform for persistence. The unified message subscription platform supports HTTP interface publishing messages, abstracts each message subscription platform, shields the specific message middleware implementation for microservices, and publishes the received message by calling the specific message middleware client SDK. The abstract interface is defined as follows: Push (String Topic, String Payload), and the interface contains the message topic Topic and the message content Payload. The microservice calls this interface to publish messages. After receiving the subscribed message, the unified message subscription platform retrieves the WebHook interface corresponding to the persistent Topi and initiates a request to this interface. When making the request, the received Payload message is put into the Body (request body) of the Post method interface as it is. After receiving the request, the WebHook interface of the microservice executes the business volume logic of the subscription data.

[0042] Regarding business logic / traffic logic, it should be noted that after subscribing to a message, the specific actions depend on the needs of the application and the type of message. Including but not limited to the following operations and processing flows: 1. Processing message content: Parse the message content and extract useful information. Execute the corresponding business logic according to the message type. 2. Update the database: Update the database records according to the message content, such as user information, order status, etc. 3. Trigger business processes: Start or trigger specific business processes, such as payment processes, workflows, etc. 4. User notification: Send notifications to users, such as via email, SMS, or in-app notifications. 5. Data synchronization: In a distributed system, synchronize the data status between different services or components. 6. Logging: Record logs of message reception and processing for auditing and troubleshooting. 7. Error handling: Implement error handling mechanisms such as retry logic, exception capture, and alarm notifications. 8. Feedback confirmation: Send a confirmation message to the message sender, indicating that the message has been successfully received and processed. 9. Status tracking: Update the system status, track task progress or event status. 10. Data analysis: Analyze the message data to extract insights or generate reports. 11. User interface update: Update information on the user interface in real time to provide instant feedback. 12. Call external services: Call external APIs or services based on the message content. 13. Load balancing: Under high load conditions, assign tasks to different processing units. 14. Security check: Verify the security and integrity of the message to ensure that the message has not been tampered with. 15. Message persistence: Store the message in persistent storage for subsequent processing or auditing. It should be noted that in actual applications, the operations after subscribing to the message may involve one or more of the above steps, depending on the complexity of the system and business requirements. These operations are implemented through a message handler, which executes the corresponding business logic when receiving the subscribed message.

[0043] Through this solution, the coupling between microservices and message middleware is greatly reduced, and the flexibility and maintainability of the system are improved. Microservices are no longer restricted by specific message middleware versions, and no longer need to face the large amount of code modifications caused by switching between different message middleware. Compared with the status before the improvement, this solution brings the following beneficial effects: (1) Reduced integration cost: Through the unified message subscription platform and WebHook interface registration mechanism, the integration cost of microservices and message middleware is reduced. (2) Microservices do not need to adapt to different message middleware versions, nor do they need to modify a large amount of code due to switching message middleware. (3) Improved system flexibility: The improved solution makes the system more flexible and scalable. Microservices can more easily adapt to different message middleware platforms without worrying about the difficulty of system expansion due to excessive coupling. (4) Simplified maintenance work: After the improvement, the maintenance work of the system becomes simpler. Microservices are no longer restricted by specific message middleware, and maintenance personnel can also manage the entire message subscription system more easily.

[0044] In another preferred embodiment, reference Figure 2 The message subscription device based on the unified message subscription platform of this embodiment includes at least one microservice (such as Figure 2 As shown, it includes microservice A and microservice B) and a unified message subscription platform, each microservice is provided with a WebHook interface, wherein: the unified message subscription platform is used to: upon receiving a subscription registration request of a microservice, bind the WebHook interface of the microservice with a preset target topic and register it in the unified message subscription platform to achieve persistence. When subscribing to the subscription data of the preset target topic, a data push POST request is initiated to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice. The microservice is used to: execute the business logic corresponding to the subscription data based on the data push POST request received by its WebHook interface.

[0045] This embodiment can realize real-time message subscription without introducing a specific message middleware client SDK in the microservice, thereby improving the scalability and adaptability of the system, effectively solving the problem of message middleware version sensitivity and code modification during switching, reducing the cost of system integration and maintenance, reducing the coupling between microservices and message middleware, and improving the flexibility and maintainability of the system.

[0046] In another preferred embodiment, the computer-readable storage medium of this embodiment stores a computer program, and the computer program is suitable for being loaded by a processor to execute the steps of the message subscription method based on a unified message subscription platform as in the above embodiment.

[0047] This embodiment can realize real-time message subscription without introducing a specific message middleware client SDK in the microservice, thereby improving the scalability and adaptability of the system, effectively solving the problem of message middleware version sensitivity and code modification during switching, reducing the cost of system integration and maintenance, reducing the coupling between microservices and message middleware, and improving the flexibility and maintainability of the system.

[0048] In another preferred embodiment, the computer device of this embodiment includes a memory and a processor, the memory stores a computer program, and the processor executes the steps of the message subscription method of the unified message subscription platform of the above embodiment by calling the computer program stored in the memory.

[0049] This embodiment can realize real-time message subscription without introducing a specific message middleware client SDK in the microservice, thereby improving the scalability and adaptability of the system, effectively solving the problem of message middleware version sensitivity and code modification during switching, reducing the cost of system integration and maintenance, reducing the coupling between microservices and message middleware, and improving the flexibility and maintainability of the system.

[0050] The computer-readable storage medium of the present invention can be any computer-readable storage medium that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0051] The processor of the present invention is used to provide computing and control capabilities to support the operation of the entire device. It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0052] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0053] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0054] It can be understood that the above embodiments only express the preferred implementation modes of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the patent scope of the present invention. It should be pointed out that, for ordinary technicians in this field, the above technical features can be freely combined without departing from the concept of the present invention, and several deformations and improvements can be made, which all belong to the protection scope of the present invention. Therefore, all equivalent changes and modifications made to the scope of the claims of the present invention should belong to the coverage of the claims of the present invention.

Claims

1. A message subscription method based on a unified message subscription platform, characterized in that: Each microservice is set up with a WebHook interface, including the following steps: S1. When the unified message subscription platform receives a subscription registration request from a microservice, the WebHook interface of the microservice is bound to a preset target topic and registered in the unified message subscription platform to achieve persistence; S2. When the unified message subscription platform subscribes to the subscription data of the preset target topic, it initiates a data push POST request to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice; S3. The microservice pushes the POST request based on the data received by its WebHook interface and executes the business logic corresponding to the subscription data.

2. The message subscription method according to claim 1, characterized in that: Before the unified message subscription platform receives the subscription registration request of the microservice, the method further includes: Abstract multiple message subscription platforms to build a unified message subscription platform for publishing messages through a unified interface; one message subscription platform corresponds to one message middleware.

3. The message subscription method according to claim 1, characterized in that: Step S2 includes: When the unified message subscription platform subscribes to the subscription data of the preset target topic, the subscription data is placed in the request body, and a data push POST request is initiated, so that the subscription data is transmitted together with the data push POST request to the WebHook interface of the corresponding microservice.

4. The message subscription method according to claim 1, characterized in that: Step S3 also includes: When the microservice receives the data push POST request based on its WebHook interface, it responds within a preset time period, and after completing the response, executes the business logic corresponding to the subscription data.

5. The message subscription method according to claim 4, characterized in that: The preset duration is less than 3 seconds.

6. The message subscription method according to claim 4, characterized in that: The step of responding within a preset time period includes: The microservice sends a response result containing an HTTPStatus status code to the unified message subscription platform within a preset time period; the HTTPStatus status code is used to identify whether the request is successful.

7. The message subscription method according to claim 6, characterized in that: When the HTTPStatus status code is 200, it means that the data push POST request is successful.

8. A message subscription device based on a unified message subscription platform, characterized in that: It includes at least one microservice and a unified message subscription platform. Each microservice is provided with a WebHook interface, wherein: The unified messaging subscription platform is used for: When receiving a subscription registration request of a microservice, the WebHook interface of the microservice is bound to a preset target topic and registered in the unified message subscription platform to achieve persistence; When subscribing to the subscription data of the preset target topic, a data push POST request is initiated to the WebHook interface corresponding to the preset target topic to transmit the subscription data to the microservice; The microservice is used to: execute the business logic corresponding to the subscription data based on the data push POST request received by its WebHook interface.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is suitable for being loaded by a processor to execute the steps of the message subscription method based on a unified message subscription platform as claimed in any one of claims 1 to 7.

10. A computer device, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the steps of the message subscription method based on the unified message subscription platform as claimed in any one of claims 1 to 7 by calling the computer program stored in the memory.

Images