CN116225735A - Extension method of message-driven programming model based on Spring Cloud Stream - Google Patents

Abstract

The invention discloses an extension method of a message-driven programming model based on SpringCloudStream, comprising the following steps: S1, starting the Spring project, initializing the environment configuration of the message queue middleware; S2, initializing the configuration of the message queue consumer and invoking the built-in message queue consumption The processor will dynamically create a message input channel, which will be registered in the Spring container; S3, use the @MQListener annotation method to dynamically create and cache the message subscription channel; S4, after the Spring project is started, traverse the cache in the message subscription channel for message queuing Binding and starting of the consumer; S5. Initialize the configuration of the message queue producer, call the built-in message queue producer processor to dynamically create and bind the message output channel, and send the message. The method of the present invention realizes the feature of dynamically creating and binding message channels in message production and message consumption, thereby supporting more flexible message-driven business scenarios.

Description

Extension method of message-driven programming model based on Spring Cloud Stream

technical field

The invention relates to the field of computer technology, in particular to an extension method of a message-driven programming model based on Spring Cloud Stream.

Background technique

Spring Cloud Stream is a framework for building message-driven microservices, which solves the problem of developers using various message middleware without awareness. Spring Cloud Stream relies on configuration adjustments to support the dynamic switching of different types of message middleware and the maintenance of corresponding message channels (including default message channels or custom message channels), so that applications can pay more attention to their own business implementation.

At present, the programming model of Spring Cloud Stream is to bind the message channel through the configuration file in advance, and then inject and annotate the Spring Bean (the management object of the framework runtime) in the consumption processing class of message production and message monitoring. Realize the display and declaration of the corresponding message channel. The problem with this method is that it is impossible to dynamically create and bind message channels in the consumption of message production and message monitoring. When the program needs to dynamically switch to the corresponding MQ consumer and MQ producer according to dynamic operating conditions (such as group ID) (MQ, Message Queue, that is, message queue), it is necessary to use the method of pre-configuring the message input/output channel. Not only the configuration items are lengthy and complicated, it is difficult to maintain, but also a large number of supporting class files with the same function need to be created, resulting in a large number of program files. Increase rapidly.

Contents of the invention

In order to solve the above problems, the present invention provides an extension method of the message-driven programming model based on Spring Cloud Stream.

The present invention adopts following technical scheme:

The extension method of the message-driven programming model based on Spring Cloud Stream includes the following steps:

S1. Start the Spring project and initialize the environment configuration of the message queue middleware;

S2. In the initialization callback method of the Spring Bean life cycle, initialize the configuration of the message queue consumer and call the built-in message queue consumer processor to dynamically create a message input channel, which will be registered in the Spring container;

S3. In the post-processor initialization callback method of the Spring Bean life cycle, the @MQListener annotation method is used to dynamically create and cache the message subscription channel;

S4. After the Spring project is started, traverse the cache in the message subscription channel to bind and start the message queue consumer;

S5. Initialize the configuration of the message queue producer, call the built-in message queue producer processor to dynamically create and bind the message output channel, and send the message.

Further, the environment configuration of the message queue middleware includes a default binder and a binder list message under the Spring Cloud Stream configuration item.

Further, the binder list information includes message queue producer policy configuration information, message queue consumer policy configuration information and message queue server connection information.

Further, the configuration of the message queue consumer includes channel topics, exception retry policies, consumption groups and binders.

Further, the message subscription channel is used to monitor messages in the message queue under the corresponding channel topic of the message queue consumer.

Further, the Spring Bean life cycle includes instantiation, property filling and initialization of Bean objects during the startup phase of the Spring project.

Further, in step S4, start message queue consumers one by one only when all message queue consumers in the cache in the message subscription channel are successfully bound, and stop all message queue consumption if any message queue consumer fails to start the startup of the

Further, the configuration of the message queue producer includes channel topics, producer groups and binders.

Further, the built-in message queue consumer processor is used to uniformly execute the dynamic creation of the message input channel and the registration of the Bean logic of the message queue consumption monitoring processor.

Furthermore, the built-in message queue producer processor is used to uniformly execute the dynamic creation of the message output channel, the registration of the Bean logic of the message queue producer processor and the binding of the message output channel.

After adopting the technical solution, the present invention has the following advantages compared with the background technology:

The present invention extends the message-driven programming model of Spring Cloud Stream, so that it has the characteristics of dynamically creating and binding message channels in message production and message consumption, thereby supporting more flexible message-driven business scenarios.

Description of drawings

Fig. 1 is a flow chart of the method of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

Example

As shown in Figure 1, the extension method of the message-driven programming model based on Spring Cloud Stream includes the following steps:

S1. Start the Spring project and initialize the environment configuration of the message queue middleware;

The environment configuration of the message queue middleware includes a default binder and a binder list message under the Spring Cloud Stream configuration item. The binder list information includes message queue producer policy configuration information, message queue consumer policy configuration information and message queue server connection information.

S2. In the initialization callback method of the Spring Bean life cycle, initialize the configuration of the message queue consumer and call the built-in message queue consumer processor to dynamically create a message input channel, which will be registered in the Spring container;

The configuration of the message queue consumer includes channel topic, exception retry policy, consumption group and binder. The built-in message queue consumer processor is used to uniformly execute the dynamic creation of the message input channel and the registration of the Bean logic of the message queue consumption monitoring processor.

S3. In the post-processor initialization callback method of the Spring Bean life cycle, the @MQListener annotation method is used to dynamically create and cache the message subscription channel;

The message subscription channel is used to monitor messages in the message queue under the corresponding channel topic of the message queue consumer. The Spring Bean life cycle includes the Bean object instantiation, attribute filling and initialization process in the startup phase of the Spring project.

S4. After the Spring project is started, traverse the cache in the message subscription channel to bind and start the message queue consumer;

In step S4, start the message queue consumers one by one only after all the message queue consumers in the cache in the message subscription channel are successfully bound, and stop the startup of all message queue consumers if any message queue consumer fails to start .

S5. Initialize the configuration of the message queue producer, call the built-in message queue producer processor to dynamically create and bind the message output channel, and send the message.

The configuration of the message queue producer includes channel topic, producer group and binder. The built-in message queue producer processor is used to uniformly execute the dynamic creation of the message output channel, the registration of the Bean logic of the message queue producer processor and the binding of the message output channel.

This embodiment extends the message-driven programming model of Spring Cloud Stream so that it has the feature of dynamically creating and binding message channels in message production and message consumption, thereby supporting more flexible message-driven business scenarios.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present invention can easily think of changes or Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. The expansion method of the message driven programming model based on Spring Cloud Stream is characterized by comprising the following steps of: the method comprises the following steps:

s1, starting a Spring item, and initializing environment configuration of a message queue middleware;

s2, initializing configuration of a message queue consumer and calling a built-in message queue consumer processor to dynamically create a message input channel in an initialization callback method of a Spring Bean life cycle, and registering the message input channel in a Spring container;

s3, dynamically creating and caching a message subscription channel by adopting an @ MQListener annotation method in a post processor initialization callback method of a Spring Bean life cycle;

s4, after the Spring item is started, traversing the cache in the message subscription channel to bind and start the message queue consumer;

s5, initializing the configuration of the message queue producer, calling the built-in message queue producer processor to dynamically create and bind the message output channel, and sending the message.

2. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 1, further comprising: the environment configuration of the message queue middleware includes default binder and binder list messages under Spring Cloud Stream configuration items.

3. The method of expanding a message driven programming model based on Spring Cloud Stream of claim 2, further comprising: the binder list information includes message queue producer policy configuration information, message queue consumer policy configuration information, and message queue server connection information.

4. The method for expanding a message driven programming model based on Spring Cloud Stream of claim 3, further comprising: the message queue consumer's configuration includes channel topic, special retry policy, consumer group, and binder.

5. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 4, wherein: the message subscription channel is used for monitoring messages in the message queue under the corresponding channel theme of the message queue consumer.

6. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 5, further comprising: the Spring Bean life cycle comprises the steps of carrying out the instantiation, attribute filling and initialization of Bean objects in the starting stage of the Spring project.

7. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 6, wherein: in step S4, the message queue consumers are started one by one only after all the message queue consumers in the buffer memory in the message subscription channel are successfully bound, and if any one message queue consumer fails to start, the starting of all the message queue consumers is stopped.

8. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 7, wherein: the message queue producer's configuration includes channel topics, producer groupings, and binders.

9. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 8, wherein: the built-in message queue consumer processor is used for uniformly executing dynamic creation of a message input channel and registration of Bean logic of the message queue consumption monitoring processor.

10. The method of extension of a Spring Cloud Stream-based message-driven programming model of claim 9, wherein: the built-in message queue producer processor is used for uniformly executing dynamic creation of the message output channel, registration of Bean logic of the message queue producer processor and binding of the message output channel.

Images