News for hackers. Stuff that matters.
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by zerbinxx on Wednesday September 20, 2023 @01:15AM (#37580598)
Jetstream does indeed have message persistence: I can issue queries like “get messages on topic since 5 minutes ago” - I do this a ton. However, that seems to be the extent of the storage/query API that it exposes for historical messages. I’m quite a big fan, and would recommend it with the caveat that Jetstream is considerably more complex than simple nats and I get the feeling I’m barely scratching the surface with it.
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by doctor_eval on Wednesday September 20, 2023 @07:09AM (#37582747)
I’m really interested in a Kafka like message broker in the Go ecosystem and look forward to checking it out for whatever my next project ends up being.
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by zerbinxx on Sunday September 24, 2023 @02:11AM (#37630562)
It’s pretty cool. I would personally suggest Kafka or RabbitMQ depending on your needs, as Jetstream has proven to require a lot of ops engineering to remain stable in production
Re:RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1) by rcombatwombat on Thursday September 21, 2023 @07:41PM (#37605961)
NATS JetStream also implements subject-based addressing at the stream level (unlike Kafka where 1 stream = 1 topic, and you can only use the message's key for distribution, not for addressing).

So you can for example ask for [the first/the last/all] of the messages on a particular subject, or on a hierarchy of subjects by using wildcards. All the filtering is done at the server level.