4 ms·

So there is base NATS and abstractions built upon NATS. Which are you referring to? There's documentation on this bug/feature[0] and it looks like using NATS s

So there is base NATS and abstractions built upon NATS. Which are you referring to? There's documentation on this bug/feature[0] and it looks like using NATS streaming is a way to fix this. I will admit that it's a bit annoying to figure out the difference between NATS streaming, jetstream and Liftbridge but I don't think this issue affects all 3. Jetstream is essentially NATS streaming built into the NATS binary itself, so switching to it should produce the feature set you're looking for. [0]: https://docs.nats.io/nats-server/nats_admin/slow_consumers https://docs.nats.io/nats-server/nats_admin/slow_consumers

oaiey 5y ago
Completely agree with that. I was referring base NATS. RabbitMQ plays in the field of traditional general purpose messaging system. NATS was specializing on performance. Kafka focused on streams. That is a focus and includes trade offs. Which is all fine. That is all I want to address.
atombender 5y ago
NATS JetStream is very different, implementation-wise, from NATS Streaming. The latter is deprecated and no longer under development. JetStream is impressive and looks very promising. I did some stress testing recently and found some performance issues and possible bugs, but I wouldn't hesitate to put it into production.