- 01
DESIGN TEMPLATES
In case of incorrect shutdown of the server, the data in the queue is not lost, processing continues from the place where there was a cliff
- 02
EASY TO USE
Distribute tasks to multiple queues, i.e. create message-level parallelization
- 03
A LOT OF TOOLS
If the processing result is not satisfactory, the task can be sent to the queue again
- 04
DISCONNECTED COMPONENTS
There are several modes of operation of the queue: point-to-point (direct) type distribution, topic-based distribution of messages (fanout)
- 05
SEPARATED LOGIC
The ability to synchronize the work of the client and the server, a kind of implementation of RPC
- 06
FULL TESTED
The number of messages stored in the queue is unlimited
- 07
MOBILE READY
The message server can be located remotely with respect to both the producer and the concierge
RABBITMQ.
RabbitMQ is the one of the most widely deployed open source message brokers. RabbitMQ is lightweight and easy to deploy on premises and in the cloud. It supports multiple messaging protocols. RabbitMQ can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements.Why RabbitMQ? There are several reasons, but one of the main reasons is the implementation of the application on the Erlang / OTP platform, which guarantees maximum stability and scalability of the queue, as a key node of the entire system. Another reason is the complete openness of the application distributed under the Mozilla Public License and the implementation of the open AMQP protocol, libraries for which exist in all major programming languages and platforms. Including for Node.js