When using asynchronous communication for Microservices, it is common to use a message broker. A broker ensures communication between different microservices is reliable and stable, that the messages…

ekangal

Domain-Driven Design

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

There are two common ways Microservices communicate with each other: Synchronous and Asynchronous. RabbitMQ was released in 2007 and is one of the first common message brokers to be created. RabbitMQ is an open-source that delivers messages through both point-to-point and pub-sub methods.

Redis vs Kafka vs RabbitMQ

Microservices Communication: Synchronous and Asynchronous

<p>I personally think Kafka can replace RabbitMQ in most cases without to much extra work. Redis has functionality very different from Kafka that makes it useful. That said, I have minimal experience with RabbitMQ because Kafka and Redis have always been perfect options for me. There may be scenarios where RabbitMQ is the clear winner for more reasons than package dependencies, but that hasn’t happened for me yet.</p>


<p>Interesting I would never have compared Redis to Kafka. I kind of feel they are different use cases and situations.</p>
