Needs advice
on
KafkaKafkaRabbitMQRabbitMQ
and
RedisRedis

Hello! [Client sends live video frames -> Server computes and responds the result] Web clients send video frames from their webcam then on the back we need to run them through some algorithm and send the result back as a response. Since everything will need to work in a live mode, we want something fast and also suitable for our case (as everyone needs). Currently, we are considering RabbitMQ for the purpose, but recently I have noticed that there is Redis and Kafka too. Could you please help us choose among them or anything more suitable beyond these guys. I think something similar to our product would be people using their webcam to get Snapchat masks on their faces, and the calculated face points are responded on from the server, then the client-side draw the mask on the user's face. I hope this helps. Thank you!

READ LESS
3 upvotes·403.7K views
Replies (3)
Senior software architect at Bootloader·
Recommends
Kafka

For your use case, the tool that fits more is definitely Kafka. RabbitMQ was not invented to handle data streams, but messages. Plenty of them, of course, but individual messages. Redis is an in-memory database, which is what makes it so fast. Redis recently included features to handle data stream, but it cannot best Kafka on this, or at least not yet. Kafka is not also super fast, it also provides lots of features to help create software to handle those streams.

READ MORE
3 upvotes·2 comments·403.4K views
Jordi Martínez
Jordi Martínez
·
January 21st 2020 at 8:45PM

Sorry for the typos, I meant “, but it cannot beat Kafka on this, or at least not yet. Kafka is also super fast, and it also ...”

·
Reply
Alikhan Oitan
Alikhan Oitan
·
March 17th 2020 at 9:15AM

Thank you very much for the clear explanation! I will definitely note the recommendation!

·
Reply
Recommends
RabbitMQ

I've used all of them and Kafka is hard to set up and maintain. Mostly is a Java dinosaur that you can set up and. I've used it with Storm but that is another big dinosaur. Redis is mostly for caching. The queue mechanism is not very scalable for multiple processors. Depending on the speed you need to implement on the reliability I would use RabbitMQ. You can store the frames(if they are too big) somewhere else and just have a link to them. Moving data through any of these will increase cost of transportation. With Rabbit, you can always have multiple consumers and check for redundancy. Hope it clears out your thoughts!

READ MORE
2 upvotes·1 comment·403.1K views
Alikhan Oitan
Alikhan Oitan
·
March 17th 2020 at 9:16AM

Thanks a lot for the recommendation! I will to note that!

·
Reply
View all (3)
Avatar of Jordi Martínez

Jordi Martínez

Senior software architect at Bootloader