Messaging middleware those things --RabbitMQ

Message Queue has gradually become the core of enterprise IT means of internal communication systems. It has a low coupling, reliable delivery, broadcast, traffic control, eventual consistency and a series of functions, one of the main means of asynchronous RPC. There are many of today's mainstream messaging middleware, such as veteran's ActiveMQ, RabbitMQ, hot Kafka, Alibaba developed RocketMQ and so on.

Mainstream messaging middleware comparison:

Comparison summary as follows:

General business systems to be introduced MQ, the earliest we all use ActiveMQ, but now we do not much use, no proven large-scale throughput scene, the community is not very active, so we still forget it, I personally do not We recommend the use of this;

Later, it began to use RabbitMQ, but it does prevent a lot of erlang language java engineer to control his in-depth study and, for companies, almost in an uncontrollable state, but who is really open source, relatively stable support activity also high;

It is indeed more and more companies will go with RocketMQ, really good, but I want to remind myself good community risk in case of a sudden yellow out of their own company's technology strength have absolute confidence, I recommend using RocketMQ, otherwise go back and honestly with RabbitMQ it, who is active in the open source community, will not yellow so small and medium companies, technical strength is more general, the technical challenges are not particularly high, with RabbitMQ is a good choice; large companies, infrastructure, strong R & D capabilities, with RocketMQ is a good choice;

If it is calculated in real time big data field, log collection and other scenes, with Kafka is the industry standard and is definitely no problem, a high degree of community activists, will not yellow, not to mention the fact that almost the norm all over the world in this field.

RabbitMQ mature than Kafka, on the availability, reliability, stability, better than theoretically RabbitMQ Kafka, since Kafka is designed to process the log, the log can be seen (message) a key component of the system, highly targeted, While the throughput is much higher than RabbitMQ, but the business side test to consider is recommended to choose RabbitMQ.

References:

https://blog.csdn.net/leexide/article/details/80035462

https://blog.csdn.net/luckyzhoustar/article/details/50411500

https://blog.csdn.net/java_zyq/article/details/80022391

https://blog.csdn.net/kingmax54212008/article/details/51706128

https://www.jianshu.com/p/5192654fc0a7

https://www.jianshu.com/p/be2958745054

http://www.80iter.com/blog/1437455520862503

Guess you like

Origin www.cnblogs.com/boxy/p/11511929.html