Do general flow diagram for the technical implementation;
Integrated cabinets, back-end call
Integrated cabinet directly from Http ways to invoke back-end services
Express back-end call cabinet
RabbitMQ is using technology to do
RabbitMQ Use
Using publish-subscribe functionality, RabbitMQ will be more reliable than redis message, the message has been preserved, floor-to-server disk.
Explanation
Subscribe to publish basic concepts:
Exchange while there is a definition of the type to decide in the end what Queue qualify, you can receive messages:
topic: All eligible routingKey (this time can be an expression) routingKey the bind message may be received in queue
This time is more queues.
PS: This and the previous statement is wrong, correct, indeed multiple queues, a non-queue. Cabinet to receive a respective message according to the routing rules.
Courier cabinet calls to the backend
Using Http way to call, but in the process, I think it should not have this scenario. If necessary, you can use http interface calls.