Why use RabbitMQ
- [Narrator] When we have a distributed system, that we want to integrate with a message broker, RabbitMQ is only one of the options. Top three message brokers are: ActiveMQ; AWS Simple Queue Service by Amazon; and Azure Service Bus. These are all great products and they may fit your needs. I won't tell you which is better. But, we'll take a quick look at some great features of RabbitMQ. RabbitMQ supports clustering. This means that you can handle heavy loads but still appear to be a single logical broker to the client applications. A client will have a list of node addresses that connect to a single node. When a node fails, the client will simply be able to connect to another node. Publishers and consumers don't have to be connected to the same node. A RabbitMQ will ensure that messages are routed the correct nodes. In the case of a node failure in a cluster, any messages and queues on this node will be lost. Highly available queues, are the answer to this. If you need it. In the case of a node failure, the other queues will contain any undelivered messages and applications will still receive them. RabbitMQ provides several other features that might be interesting to you. It supports different messaging protocols. It also runs on many platforms, as we'll see later. And there are RabbitMQ client libraries for most popular programming languages. RabbitMQ also includes a Management UI, that is easy to use. It allows you to configure and monitor RabbitMQ. If you're having any issues, with RabbitMQ, it's possible to enable tracing. If you're missing a feature, RabbitMQ includes several plugins to add functionality. And it is possible to write your own. RabbitMQ is free and open source. But, if necessary, Pivotal, which is the company behind RabbitMQ, can provide commercial support, consulting and training. You can find all of this, and much more on the Rabbit MQ website.
No comments:
Post a Comment