---
title: "Discussion on \"Why We Chose RabbitMQ Instead of Kafka for Our Distributed Scientific Data Pipeline \" | Hashnode"
description: "Discussion on \"Why We Chose RabbitMQ Instead of Kafka for Our Distributed Scientific Data Pipeline \". Understanding the problem before choosing the technology."
url: "https://hashnode.com/posts/why-we-chose-rabbitmq-instead-of-kafka-for-our-distributed-scientific-data-pipeline/6a64edbaa332293340ea644c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why We Chose RabbitMQ Instead of Kafka for Our Distributed Scientific Data Pipeline](https://understandingsystems.hashnode.dev/why-we-chose-rabbitmq-instead-of-kafka-for-our-distributed-scientific-data-pipeline?utm_source=hashnode&utm_medium=feed)

Understanding the problem before choosing the technology.

Jul 25 · 6 min read · understandingsystems.hashnode.dev  
Read the article

-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)
-   [#rabbitmq](https://hashnode.com/tag/rabbitmq)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#python](https://hashnode.com/tag/python)

## Written by

[Jay Solanki](https://hashnode.com/@jay-s9)

@jay-s9 · India

  
[View profile](https://hashnode.com/@jay-s9)

I write about software architecture, distributed systems, and the engineering decisions behind modern software. Most of my articles begin with a question I encountered while building real projects: Why this architecture? Why this technology? What problem does it actually solve? Rather than focusing only on implementation, I explore the reasoning, trade-offs, and first principles behind architectural decisions, messaging systems, data infrastructure, and scalable software design. My goal is simple: to understand the why behind technology—and share that understanding with others.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
