For ribbitmq message queues
Usage:
Define a queue as a message queue
Producer, add production messages to the queue
Consumer, after listening to a message in the message queue, retrieve the message to process the message
You can configure multiple consumers to process messages on each server.
The consumer object added to handler is similar to the observer mode.
Can it be changed to "handler", "consumer object holding", and "consumer object holding" factory or pool holding "?
When a consumer thread is started to execute a task, the main thread or the listener thread is enabled to monitor the message processing speed. Based on the message processing speed, the consumer factory is called, generate more consumers to process tasks
Similarly, if it is a server cluster, microservice can be started very quickly when microservices are prevalent today,
You can also configure a listening server to monitor the speed of tasks processed by each message queue,
Then, start more servers to process tasks based on the message processing speed.
Message Queue ideas in the distributed big data environment of ribbitmq