Modern Messaging Queues – RabbitMQ, NATS and NATS Streaming
Poojya J Bhat1, Priya D2

1Poojya J Bhat, Student, R V College of Engineering, Bangalore, India.
2Priya D, Assistant Professor, R V College of Engineering, Bangalore, India.

Manuscript received on July 19, 2020. | Revised Manuscript received on July 23, 2020. | Manuscript published on July 30, 2020. | PP: 402-408 | Volume-9 Issue-2, July 2020. | Retrieval Number: B3551079220/2020©BEIESP | DOI: 10.35940/ijrte.B3551.079220
Open Access | Ethics and Policies | Cite | Mendeley
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC BY-NC-ND license (

Abstract: Distributed messaging structures shape the core of massive microservice architecture , cloud native applications and data streaming as they are used to communicate between different application services. With actual-time crucial programs there is a developing need for well-constructed messaging platform this is fault tolerant, has low latency and scalable. This paper surveys various message broker that are in vogue today. These modern message brokers have their own adavantages and disadvantages that have come up lately. There is need for the comparative study to decide which broker is most suitable for a specific appalication. An in-depth study is required to decide which features of a messaging system meet the needs of the application. The paper outlines information about three messaging systems – RabbitMq, Nats and Nats-Streaming and explores the features they offer as well as their performance under varied testing workloads.
Keywords: NATS, NATS-Streaming, RabbitMQ, distributed messaging systems.