Shulou(Shulou.com)05/31 Report--

This article mainly shows you the "sample analysis of the message agent RabbitMQ framework", which is easy to understand and clear. I hope it can help you solve your doubts. Let the editor lead you to study and study the "sample analysis of the message agent RabbitMQ framework".

Message broker RabbitMQ framework message broker middleware

At present, there are many message broker middleware (hereinafter referred to as message broker) on the market, such as ActiveMQ, RabbitMQ, Kafka and so on. When using these frameworks, we need to call their API to send and receive messages. The general structure is shown in figure 8-1.

Figure 8-1 message broker

The message agent is mainly used to receive and forward messages, which can be regarded as the post office, the message producer as the sender and the message consumer as the recipient. When we put a letter into the mailbox, the postman will eventually deliver the letter to the recipient, RabbitMQ and other frameworks, that is, the mailbox, postman and post office work, but they do not deal with letters, but "messages".

String Cloud Sream adds an agent-like role between producers and consumers, which directly interacts with message agents (post offices). Message producers (senders) and message consumers (recipients) no longer need to directly call the API of each message broker framework, and they do not even feel the existence of message agents. The structure is similar to that in figure 8-2.

Figure 8-2 structure after using Spring Cloud Stream

After using the Stream framework, the producers and consumers of messages can pay more attention to their respective business. As to how the messages (letters) are delivered and which message agent (post office) is used, they do not need to care.

At present, the binder of Spring Cloud Stream provides the implementation of two message broker middleware, RabbitMQ and Kafka. Next, let's take a brief look at the RabbitMQ and Kafka framework.

RabbitMQ and AMQP

RabbitMQ is a lightweight message broker middleware, which supports a variety of message communication protocols and distributed deployment. At the same time, it also supports running on multiple operating systems, flexibility, high availability and other features, which makes RabbitMQ popular.

RabbitMQ supports a variety of protocols, the most important of which is the Advanced message queuing Protocol (AMQP). AMQP is an abbreviation for "Advanced Message Queuing Protocol", which defines the communication protocol between "message client" and "message broker middleware". Based on this protocol, message client and message broker middleware can be free from the constraints of development language and specific products. Before learning to use RabbitMQ, make a simple understanding of AMQP's model.

In the previous section, the message producer delivers the message to the message broker, and the message agent sends it to the message consumer. Now the message broker is further refined. The general model of AMQP is shown in figure 8-3.

Figure 8-3 AMQP model

In figure 8-3, the producer delivers the message to the "message broker (RabbitMQ server)". A message channel (Channel) is established between them, and the message is processed first by the switch (Exchange), which chooses which queue to send the message to (Message Queue). Finally, the message queue sends the message to the consumer. Next, download and run the server on which RabbitMQ is running.

Download and run

This chapter uses the RabbitMQ server version 3.6.11 (Windows), because the RabbitMQ server uses the Erlang language, so also download Erlang, this chapter uses the Erlang version for 20.0 (64-bit), download Erlang, you will get otp_win64_20.0.exe such installation files, installation files can be found in the book / soft directory, the author has downloaded 32-bit and 64-bit installer.

If you install 32-bit Erlang on a Windows 64-bit system, you will encounter an exception when using RabbitMQ.

After installing Erlang and RabbitMQ in turn, RabbitMQ starts as a Windows service. Enter "C:\ Program Files\ RabbitMQ Server\ rabbitmq_server-3.6.11\ sbin" through the Windows command line, and enter "rabbitmq-plugins list" to view the plug-in status of the current RabbitMQ. In order to use the RabbitMQ console, enter "rabbitmq-plugins enable rabbitmq_management" to open the management plug-in, and normally the following information will be output:

Applying plugin configuration to rabbit@AY-PC... Nothing to do.

Open the browser and visit the following address: http://localhost:15672, you can see the login interface of RabbitMQ. The default user name and password are "guest". After logging in, the main interface is shown in figure 8-4.

Figure 8-4 RabbitMQ main interface

At this point, the RabbitMQ server is running successfully, and the server is a message broker middleware. Next, we can write the producers and consumers of the message and use RabbitMQ's API to test the message.

The above is all the content of the article "sample Analysis of the message Agent RabbitMQ Framework". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.