The latest articles on DEV Community by Kishan Limbasiya (@kishanlimbasiya). https://dev.to/kishanlimbasiya https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4008069%2F3a80cd8a-f2c0-4a21-ac3c-fa6d23cfdff3.png https://dev.to/kishanlimbasiya en Kishan Limbasiya Mon, 29 Jun 2026 11:57:16 +0000 https://dev.to/kishanlimbasiya/we-migrated-from-rabbitmq-to-kafka-in-production-heres-why-and-what-we-learned-eld https://dev.to/kishanlimbasiya/we-migrated-from-rabbitmq-to-kafka-in-production-heres-why-and-what-we-learned-eld <h1> We Migrated from RabbitMQ to Kafka in Production — Here's Why (And What We Learned) </h1> <p>When I started building backend systems with Node.js, RabbitMQ was my go-to message broker.</p> <p>It powered almost everything:</p> <ul> <li>Email queues</li> <li>Background jobs</li> <li>Automation workers</li> <li>Cron services</li> <li>Real-time processing</li> </ul> <p>It worked really well.</p> <p>But as our platform grew, we started processing significantly more events every day. More services needed the same data, our queues became larger, and scaling became increasingly difficult.</p> <p>That's when we decided to migrate part of our system from RabbitMQ to Apache Kafka.</p> <p>This article isn't about saying RabbitMQ is bad.</p> <p>It's about sharing what we learned after using <strong>both in production.</strong></p> <h2> Our Architecture </h2> <p>Our platform consisted of multiple microservices:</p> <ul> <li>Lead Processing Service</li> <li>Automation Workers</li> <li>Notification Service</li> <li>Email Service</li> <li>Analytics</li> <li>Cron Service</li> </ul> <p>Initially everything communicated through RabbitMQ.</p> node kafka eventdriven