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

DoctorKafka

3
17
+ 1
0
ZeroMQ

226
521
+ 1
72
Add tool

DoctorKafka vs ZeroMQ: What are the differences?

DoctorKafka: A service for Kafka cluster auto healing and workload balancing. DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings; ZeroMQ: Fast, lightweight messaging library that allows you to design complex communication system without much effort. 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.

DoctorKafka and ZeroMQ belong to "Message Queue" category of the tech stack.

DoctorKafka and ZeroMQ are both open source tools. ZeroMQ with 5.33K GitHub stars and 1.57K forks on GitHub appears to be more popular than DoctorKafka with 488 GitHub stars and 68 GitHub forks.

Advice on DoctorKafka and ZeroMQ
Meili Triantafyllidi
Software engineer at Digital Science · | 6 upvotes · 301.1K views
Needs advice
on
Amazon SQSAmazon SQSRabbitMQRabbitMQ
and
ZeroMQZeroMQ

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to: * Not loose messages in services outages * Safely restart service without losing messages (ZeroMQ seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

See more
Replies (2)
Shishir Pandey
Recommends
RabbitMQRabbitMQ

ZeroMQ is fast but you need to build build reliability yourself. There are a number of patterns described in the zeromq guide. I have used RabbitMQ before which gives lot of functionality out of the box, you can probably use the worker queues example from the tutorial, it can also persists messages in the queue.

I haven't used Amazon SQS before. Another tool you could use is Kafka.

See more
Kevin Deyne
Principal Software Engineer at Accurate Background · | 5 upvotes · 102K views
Recommends
RabbitMQRabbitMQ

Both would do the trick, but there are some nuances. We work with both.

From the sound of it, your main focus is "not losing messages". In that case, I would go with RabbitMQ with a high availability policy (ha-mode=all) and a main/retry/error queue pattern.

Push messages to an exchange, which sends them to the main queue. If an error occurs, push the errored out message to the retry exchange, which forwards it to the retry queue. Give the retry queue a x-message-ttl and set the main exchange as a dead-letter-exchange. If your message has been retried several times, push it to the error exchange, where the message can remain until someone has time to look at it.

This is a very useful and resilient pattern that allows you to never lose messages. With the high availability policy, you make sure that if one of your rabbitmq nodes dies, another can take over and messages are already mirrored to it.

This is not really possible with SQS, because SQS is a lot more focused on throughput and scaling. Combined with SNS it can do interesting things like deduplication of messages and such. That said, one thing core to its design is that messages have a maximum retention time. The idea is that a message that has stayed in an SQS queue for a while serves no more purpose after a while, so it gets removed - so as to not block up any listener resources for a long time. You can also set up a DLQ here, but these similarly do not hold onto messages forever. Since you seem to depend on messages surviving at all cost, I would suggest that the scaling/throughput benefit of SQS does not outweigh the difference in approach to messages there.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of DoctorKafka
Pros of ZeroMQ
    Be the first to leave a pro
    • 24
      Fast
    • 20
      Lightweight
    • 11
      Transport agnostic
    • 7
      No broker required
    • 4
      Low level APIs are in C
    • 4
      Low latency
    • 1
      Open source
    • 1
      Publish-Subscribe

    Sign up to add or upvote prosMake informed product decisions

    Cons of DoctorKafka
    Cons of ZeroMQ
      Be the first to leave a con
      • 5
        No message durability
      • 3
        Not a very reliable system - message delivery wise
      • 1
        M x N problem with M producers and N consumers

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is DoctorKafka?

      DoctorKafka can automatically detect broker failure and reassign the workload on the failed nodes to other nodes. DoctorKafka can also perform load balancing based on topic partitions's network usage, and makes sure that broker network usage does not exceed the defined settings.

      What is 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.

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

      What companies use DoctorKafka?
      What companies use ZeroMQ?
        No companies found
        See which teams inside your own company are using DoctorKafka or ZeroMQ.
        Sign up for StackShare EnterpriseLearn More

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

        What tools integrate with DoctorKafka?
        What tools integrate with ZeroMQ?
        What are some alternatives to DoctorKafka and ZeroMQ?
        Kafka Manager
        This interface makes it easier to identify topics which are unevenly distributed across the cluster or have partition leaders unevenly distributed across the cluster. It supports management of multiple clusters, preferred replica election, replica re-assignment, and topic creation. It is also great for getting a quick bird’s eye view of the cluster.
        rdkafka
        This gem is a modern Kafka client library for Ruby based on librdkafka. It wraps the production-ready C client using the ffi gem and targets Kafka 1.0+ and Ruby 2.3+.
        Kafka UI
        It is a simple tool that makes your data flows observable, helps find and troubleshoot issues faster and deliver optimal performance. Its lightweight dashboard makes it easy to track key metrics of your Kafka clusters - Brokers, Topics, Partitions, Production, and Consumption.
        KafkaHQ
        It is a Kafka GUI for topics, topics data, consumers group, schema registry, connect and more. It works with modern Kafka cluster.
        Kafdrop
        It is a web UI for viewing Kafka topics and browsing consumer groups. The tool displays information such as brokers, topics, partitions, consumers, and lets you view messages.
        See all alternatives