apache-kafkaredispublish-subscribedata-lossfire-and-forget

apache kafka vs redis as message broker in production


I want to use redis as my commit and push data pipeline instead of kafka for its speed and performance which is the result of fire and forget strategy. What if i need the speed and data safety? has anyone managed to use redis without data loss?


Solution

  • I found a very lightweight and fast replacement for both Kafka and Redis which is nats and nats streaming. After some observation on very heavy usage of nats side by side Kafka in a large company, I come to the conclusion that it is a very suitable solution. easy to maintain, safe and fast.