Efficiency of learning a little low, slowly!
Look at some of the basic concepts of it rabbmq
Publisher: generating a message
Exchange: Switch responsible for distributing the message to the queue routing according to certain rules
Queue: carrier responsible for storing the message queue for each message the message will be put into one or more queues
Consumer: the recipient is responsible for the consumption of the message data
Binding: Binding to the message queue and the routing switch according to certain rules bind
Routing Key: according to the routing switch routing keywords keywords to match your queue
Broker: AMQP server-side called Broker. In fact, Broker is the application to receive and distribute messages, that is RabbitMQ Server Message Broker
Virtual Host: Web Hosting, a group of switches (Exchange), the message queue (Queue) and related objects. Web hosting is shared the same stand-alone server domain authentication and encryption environment. At the same time a Broker where you can set up multiple vhost, as a different user privilege separation.
Channel, a channel, an independent bi-directional multiplexed data stream channel connections for a session providing the physical transmission medium. Channel is a logical connection within the connection established, if the application supports multiple threads, each thread usually create a separate channel for communication, AMQP method includes the channel id and message broker to help clients identify the channel, so the channel is completely isolated between of. Channel Connection as a lightweight operating system greatly reduces the overhead of TCP connection establishment. In each of the client's connection can create multiple Channel, Channel each task on behalf of a session.
Connection: connection, a network connection, such as TCP / IP socket connection. Channel Connection is built on top of a Connection can create multiple Channel.
The Message, the message body is the basic unit AMQP manipulated, which is produced by Producer, Broker is consumed through the Consumer. Its basic configuration has two parts: Header and Body. Header is a set various attributes on Producer added, whether these attributes can be cached Message controls, which received the Queue, how much priority the like. Body is a real need to send data, it is not visible Broker binary data stream, should not be affected during transmission
---------------------
Original: https: //blog.csdn.net/anumbrella/article/details/79920854