Kafka vs RabbitMQ legacy migration
A bank runs RabbitMQ for events. When and how would you introduce Kafka alongside it?
Answers use simple, clear English.
Quick interview answer
Keep RabbitMQ for task queues and RPC-style work queues with ack/retry. Introduce Kafka for high-volume event logs, stream processing, replay, and analytics pipelines. Bridge with outbox + dual publish during migration.
Detailed answer
Keep RabbitMQ for task queues and RPC-style work queues with ack/retry. Introduce Kafka for high-volume event logs, stream processing, replay, and analytics pipelines. Bridge with outbox + dual publish during migration. Train teams on consumer groups vs competing consumers semantics difference.
Real example & use case
Payment notifications stay Rabbit; fraud telemetry stream moves to Kafka with ksqlDB aggregates.
Pros & cons
Pros: right broker per pattern. Cons: operating two systems; dual-write period.