RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1)

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by postalrat on Tuesday September 19, 2023 @05:31PM (#37577051)

Redis isn't an option?

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by noitpmeder on Tuesday September 19, 2023 @05:37PM (#37577134)

I'd also like someone with experience to contrast redis for these use cases.

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by rafaelturk on Tuesday September 19, 2023 @05:36PM (#37577118)

Yes, Don't why is not mentioned in the article, maybe because is more barebones.

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by blindriver on Tuesday September 19, 2023 @08:37PM (#37579031)

Redis is a cache, it's not a queue.

Can you do something similar? I guess, just like you can use a highlighter to paint your house. But the semantics are not correct.

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by relay23 on Tuesday September 19, 2023 @09:20PM (#37579311)

There is Redis Streams, but certainly not without it's problems. Super obscure, not a lot of client support.

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by akvadrako on Wednesday September 20, 2023 @02:19AM (#37580975)

Or postgres. If you are under 1000 messages a second it functions well as a transactional queue.

[ Parent | on HN ]

Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by sgarland on Wednesday September 20, 2023 @08:38AM (#37583391)

Until table bloat happens.

[ Parent | on HN ]