StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. Kafka vs Mosquitto

Kafka vs Mosquitto

OverviewDecisionsComparisonAlternatives

Overview

Kafka
Kafka
Stacks24.2K
Followers22.3K
Votes607
GitHub Stars31.2K
Forks14.8K
Mosquitto
Mosquitto
Stacks136
Followers306
Votes14

Kafka vs Mosquitto: What are the differences?

Introduction

In this article, we will compare Kafka and Mosquitto, two popular messaging platforms. We will highlight their key differences and explore the specific features of each platform. This comparison will help you understand the strengths and weaknesses of both Kafka and Mosquitto, enabling you to make an informed decision about which platform best suits your messaging requirements.

  1. Scalability and Performance: Kafka is designed to handle high throughput and large-scale data processing. It provides excellent scalability by allowing distributed processing and storage across multiple nodes. On the other hand, Mosquitto is optimized for lightweight and low-latency messaging. It is suitable for situations where real-time communication and low network overhead are critical.

  2. Protocols and Messaging Patterns: Kafka uses a publish-subscribe model where messages are published to topics and then consumed by subscribers. It supports multiple protocols such as TCP, HTTP, and HTTPS, making it highly flexible. Mosquitto, on the other hand, follows the publish-subscribe pattern as well, but it primarily uses the MQTT protocol. MQTT is a lightweight and efficient protocol that is well-suited for constrained devices and resource-limited environments.

  3. Reliability and Persistence: Kafka has strong durability guarantees due to its message retention mechanism. It persists messages for a configurable period, allowing consumers to replay data or recover from failures. Kafka also provides fault-tolerant replication and ensures zero data loss. In contrast, Mosquitto provides more basic persistence options and does not have built-in support for guaranteed message delivery.

  4. Ecosystem and Integration: Kafka has a rich and mature ecosystem, with support from various third-party tools and frameworks. It integrates well with popular big data technologies like Apache Spark, Apache Hadoop, and Apache Flink. Mosquitto, although less extensive, is still well-supported and has various client libraries available for different programming languages.

  5. Use Cases and Industry Focus: Kafka is widely used in scenarios that require real-time event stream processing and high-performance data ingestion. It is commonly employed in big data analytics, data pipelines, and microservices architectures. Mosquitto is popular in the Internet of Things (IoT) domain, where it is used for lightweight and reliable device-to-device communication.

  6. Community and Documentation: Kafka has a large and active community, which leads to excellent support and a wealth of online resources. The official Kafka documentation is comprehensive and updated regularly. Mosquitto also has an active community, although it may not be as extensive as Kafka's. However, the Mosquitto documentation is well-maintained and provides all the necessary information to get started with the platform.

In summary, Kafka excels in scalability, performance, and providing durable messaging with fault-tolerance, making it suitable for large-scale data processing and real-time analytics. Mosquitto, on the other hand, focuses on lightweight messaging and is well-suited for constrained environments and IoT applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Kafka, Mosquitto

viradiya
viradiya

Apr 12, 2020

Needs adviceonAngularJSAngularJSASP.NET CoreASP.NET CoreMSSQLMSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k
Comments
Ishfaq
Ishfaq

Feb 28, 2020

Needs advice

Our backend application is sending some external messages to a third party application at the end of each backend (CRUD) API call (from UI) and these external messages take too much extra time (message building, processing, then sent to the third party and log success/failure), UI application has no concern to these extra third party messages.

So currently we are sending these third party messages by creating a new child thread at end of each REST API call so UI application doesn't wait for these extra third party API calls.

I want to integrate Apache Kafka for these extra third party API calls, so I can also retry on failover third party API calls in a queue(currently third party messages are sending from multiple threads at the same time which uses too much processing and resources) and logging, etc.

Question 1: Is this a use case of a message broker?

Question 2: If it is then Kafka vs RabitMQ which is the better?

804k views804k
Comments
Roman
Roman

Senior Back-End Developer, Software Architect

Feb 12, 2019

ReviewonKafkaKafka

I use Kafka because it has almost infinite scaleability in terms of processing events (could be scaled to process hundreds of thousands of events), great monitoring (all sorts of metrics are exposed via JMX).

Downsides of using Kafka are:

  • you have to deal with Zookeeper
  • you have to implement advanced routing yourself (compared to RabbitMQ it has no advanced routing)
10.9k views10.9k
Comments

Detailed Comparison

Kafka
Kafka
Mosquitto
Mosquitto

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

It is lightweight and is suitable for use on all devices from low power single board computers to full servers.. The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers.

Written at LinkedIn in Scala;Used by LinkedIn to offload processing of all page and other views;Defaults to using persistence, uses OS disk cache for hot data (has higher throughput then any of the above having persistence enabled);Supports both on-line as off-line processing
-
Statistics
GitHub Stars
31.2K
GitHub Stars
-
GitHub Forks
14.8K
GitHub Forks
-
Stacks
24.2K
Stacks
136
Followers
22.3K
Followers
306
Votes
607
Votes
14
Pros & Cons
Pros
  • 126
    High-throughput
  • 119
    Distributed
  • 92
    Scalable
  • 86
    High-Performance
  • 66
    Durable
Cons
  • 32
    Non-Java clients are second-class citizens
  • 29
    Needs Zookeeper
  • 9
    Operational difficulties
  • 5
    Terrible Packaging
Pros
  • 10
    Simple and light
  • 4
    Performance

What are some alternatives to Kafka, Mosquitto?

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase