---
title: "Comment by Akshay Siddhpura on \"Deep Dive of the Distributed Job Scheduler that powers over 2 Billion daily jobs at PhonePe\" | Hashnode"
description: "Any thoughts on Kafka instead of RabbitMQ.? if we use Kafka instead of RabbitMQ few task can be avoided. for example 1) Kafka by default handle leader election"
url: "https://hashnode.com/posts/deep-dive-of-the-distributed-job-scheduler-that-powers-over-2-billion-daily-jobs-at-phonepe/65d1086c135bdc53dbd20e4f/comment/65e1b71ca651b604036b3e2f"
---

[Discussion](https://hashnode.com/posts/deep-dive-of-the-distributed-job-scheduler-that-powers-over-2-billion-daily-jobs-at-phonepe/65d1086c135bdc53dbd20e4f)

Comment [Deep Dive of the Distributed Job Scheduler that powers over 2 Billion daily jobs at PhonePe](https://hashnode.com/posts/deep-dive-of-the-distributed-job-scheduler-that-powers-over-2-billion-daily-jobs-at-phonepe/65d1086c135bdc53dbd20e4f)

[Akshay Siddhpura](https://hashnode.com/@akshaysiddhpura)

[Mar 1, 2024](https://hashnode.com/posts/deep-dive-of-the-distributed-job-scheduler-that-powers-over-2-billion-daily-jobs-at-phonepe/65d1086c135bdc53dbd20e4f/comment/65e1b71ca651b604036b3e2f)

Any thoughts on Kafka instead of RabbitMQ.? if we use Kafka instead of RabbitMQ few task can be avoided. for example 1) Kafka by default handle leader election and making sure no consumers are consuming from the same partition. In case some worker node goes down partition re-balance will also happen automatically.

2)Back pressure will also be handled automatically as per consumer speed.

putting this comment to understand why RabbitMQ was selected over other solutions?

[Snehasish Roy](https://hashnode.com/@snehasishroy)

[Mar 1, 2024](https://hashnode.com/posts/deep-dive-of-the-distributed-job-scheduler-that-powers-over-2-billion-daily-jobs-at-phonepe/65d1086c135bdc53dbd20e4f/comment/65e1b71ca651b604036b3e2f#reply-65e230e596bbf62784846c99)

You are correct about backpressure being handled automatically because of pull model instead of the push model by RabbitMQ.

But you are incorrect regarding the leader election. We dont push directly to RMQ. We enqueue first to HBase and only the eligible messages are pushed to RMQ. We still would need leader election while consuming from HBase.

Any messaging queue could have been used when eligible messages are found from HBase. Kafka is ops heavy. It requires a lot of operational overhead. RMQ is very light on operations. If your organization already has a Kafka cluster then it can be used.
