MQTT vs Kafka: A Communication Between Microservices
The architecture created with the use of microservices is one of the most important breakthroughs in recent years in the world of web and software development. The modular structure assures independence of every single microservice, simplifying the deployment. This, though, has an impact on the microservices’ communication. Tools like Kafka and MQTT help tackle this challenge.
Recently microservices architecture is becoming more and more popular. Orchestration tools like Docker and Kubernetes make it very simple to create and maintain such applications. One can say that these tools are even forcing microservices architecture.
Communication between microservices
Unfortunately, such an architecture, apart from many advantages, has some challenges, too! And one of them is finding a good way of communication between microservices.
If you had such a problem, you surely heard about three solutions: REST API, MQTT or Kafka. Believe me or not, but REST API is a no-go for this use case. So we are left with two solutions: MQTT and Kafka.
Both are messaging brokers which have different protocols and serve different purposes, so let’s make a comparison of these two.
Perfect messaging broker
Let's start with things that are the most important for microservices.
Microservices should have persisted data storage. They should be able to take a high volume traffic and massive datasets. Also, they should have an ability to split the traffic into separated, logical parts, for example, topics. Lastly, microservices should have a very high reliability and events deliverability.
So with these requirements in mind let’s jump into the comparison between Kafka and Mosquitto.
Kafka was originally created by LinkedIn employees back in 2011 with their messaging system in mind. It was later distributed on the Apache License. Kafka persists events, meaning that messages are immediately written to the filesystem when they are received.
It has an ability to scale services without the fear of duplicated processing of event. Kafka scales by adding more partitions so that the messages from each partition can be processed in parallel making the tool easily and highly scalable. That’s because, from the very beginning, it was being developed for big systems. It scales better than other similar ‘stateful’ message brokers.
Kafka can easily deal with high-velocity data ingestion. On top of that, the libraries are written in the most popular languages. It has some really interesting frameworks, check out this Ruby-based one - Karafka.
Unfortunately Kafka depends on Zookeeper in order to work properly.
Let’s take a look at Mosquitto, another for communication between microservices.
Mosquitto is a very popular solution among developers. It is a lightweight protocol created for IoT projects. It is based on publish/subscribe model. The message broker is independent from other applications or libraries.
Mosquitto is licensed under EPL/END meaning that it is open source, also it is a part of the Eclipse Foundation - it’s an important factor for many projects. Mosquitto has multiple libraries in many languages, so it’s safe to say that it is quite versatile, meaning that it can be easily adapted by developers to a project.
Kafka is better suited for microservices. It has persistent storage, so events from particular topic can be replayed from the beginning allowing to introduce Event Sourcing pattern.
Check out both tools here:
Let's talk about Jamstack and headless e-commerce!
Contact us and we'll warmly introduce you to the vast world of Jamstack & headless development!
More posts in this category
Multiprocessing vs Multithreading in Ruby: Which is Better?
Can multiprocessing be a good alternative to multithreading? Sure! It depends, however, on answering the following question: does my project really need multiple processes? To get...
Aug 19· 14 min read
4 Amazing Features of Rails 6.0
Rails 6.0. is finally released. We’re excited to see all the new stuff Rails 6.0 has to offer! With regular releases of the beta versions, developers had access to the upcoming...
Apr 24· 4 min read