Hacker News Reader

Comment by manigandham | Hacker News Reader

NATS Streaming is not as well tested and has some design issues that make scaling hard. NATS itself has a new version 2 that has a protocol update and NATS Streaming should follow with a new design as well, but I would recommend other options if you want persistence.

View on HN

What are the design flaws that you have in mind? Is it ok for a couple of nodes or even then it would have trouble to keep up with a medium load? Or maybe the design flaws are to do with providing durability and other guarantees?

What other options would you recommend, that can provide at least once delivery and are lighweight enough not to require zookeeper etc?

Nats streaming isn't just a persistence layer to NATS. It's an entirely different system that basically acts as a client to NATS and then records messages it sees. Basically think of how you would design a persistent queue on top of the ephemeral NATS pub/sub and that's what NATS streaming is.

Here's a good post (and series) about distributed logs and NATS design issues: https://bravenewgeek.com/building-a-distributed-log-from-scr...

Is this what you meant ?

https://github.com/nats-io/nats-streaming-server/issues/168

Can you share some details or point to articles describing the design issues with NATS streaming?

See the other comment but this is a good post/series: https://bravenewgeek.com/building-a-distributed-log-from-scr...

Reply on news.ycombinator.com