Record operating environment of stand-alone deployment RabbltMQ

Transfer: https://www.cnblogs.com/kevingrace/p/7693042.html

A, RabbitMQ brief
in their daily work environment, whether you come across (more) between the two systems need to synchronize some data through regular tasks? Whether you call between different processes for heterogeneous systems with each other, communication problems and distress, struggling? If yes, then congratulations, message service so that you can easily solve these problems. Message Service specializes in solving multi-system data exchange (message notification / communication) issues among heterogeneous systems, you can also use it for calls between systems and services to each other, that is suitable for long-distance calls (RPC) in cloud computing clusters. There is no doubt, RabbitMQ is one of the most mainstream messaging middleware.

AMQP (Advanced Message Queuing Protocol) i.e. Advanced Message Queuing Protocol, is an open standard application-layer protocol for message-oriented middleware design. Message middleware mainly for decoupling between the components, sender of the message without knowing the user's presence information, and vice versa. AMQP main feature is a message for the queue, the routing (including point and publish / subscribe), reliability and safety. RabbitMQ AMQP is an open source implementation, server-side using Erlang language, supports a variety of clients, such as: Python, Ruby, .NET, Java, JMS, C, PHP, ActionScript, XMPP, STOMP, and support for AJAX. In a distributed system for store and forward messages, in terms of ease of use, scalability, high availability, and so doing well.

Two, CentOS7 deployed under RabbitMQ record

 

Guess you like

Origin www.cnblogs.com/hbxZJ/p/11109006.html