Need advice about which tool to choose?Ask the StackShare community!

Kafka

18.4K
17.4K
+ 1
593
VerneMQ

29
121
+ 1
6
Add tool

Kafka vs VerneMQ: What are the differences?

Developers describe Kafka as "Distributed, fault tolerant, high throughput pub-sub messaging system". Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. On the other hand, VerneMQ is detailed as "VerneMQ is a distributed IoT/MQTT message broker". VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications..

Kafka and VerneMQ can be categorized as "Message Queue" tools.

Some of the features offered by Kafka are:

  • 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)

On the other hand, VerneMQ provides the following key features:

  • Open Source, Apache 2 licensed
  • QoS 0, QoS 1, QoS 2
  • MQTT v5.0 fully implemented

Kafka and VerneMQ are both open source tools. It seems that Kafka with 12.7K GitHub stars and 6.81K forks on GitHub has more adoption than VerneMQ with 1.76K GitHub stars and 189 GitHub forks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Kafka
Pros of VerneMQ
  • 125
    High-throughput
  • 119
    Distributed
  • 89
    Scalable
  • 83
    High-Performance
  • 65
    Durable
  • 37
    Publish-Subscribe
  • 19
    Simple-to-use
  • 17
    Open source
  • 11
    Written in Scala and java. Runs on JVM
  • 8
    Message broker + Streaming system
  • 4
    Avro schema integration
  • 4
    Robust
  • 4
    KSQL
  • 2
    Suport Multiple clients
  • 2
    Partioned, replayable log
  • 1
    Flexible
  • 1
    Extremely good parallelism constructs
  • 1
    Simple publisher / multi-subscriber model
  • 1
    Fun
  • 1
    Fully open source clustering
  • 1
    Proxy Protocol support
  • 1
    Open Source Plugin System
  • 1
    Open Source Message and Metadata Persistence
  • 1
    MQTT v5 implementation
  • 1
    Open source shared subscriptions

Sign up to add or upvote prosMake informed product decisions

Cons of Kafka
Cons of VerneMQ
  • 29
    Non-Java clients are second-class citizens
  • 27
    Needs Zookeeper
  • 7
    Operational difficulties
  • 2
    Terrible Packaging
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Kafka?

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

    What is VerneMQ?

    VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP. It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Kafka?
    What companies use VerneMQ?
    See which teams inside your own company are using Kafka or VerneMQ.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Kafka?
    What tools integrate with VerneMQ?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Kafka and VerneMQ?
    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.
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    Amazon Kinesis
    Amazon Kinesis can collect and process hundreds of gigabytes of data per second from hundreds of thousands of sources, allowing you to easily write applications that process information in real-time, from sources such as web site click-streams, marketing and financial information, manufacturing instrumentation and social media, and operational logs and metering data.
    Apache Spark
    Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.
    Akka
    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
    See all alternatives