News for hackers. Stuff that matters.
Re:High-Performance server for NATS.io, the cloud and edge n... by atombender on Monday July 24, 2023 @07:54AM (#36846403)
You wouldn't/shouldn't choose NATS if your application needs different semantics.

NATS does not have stateful storage. So when a consumer disconnects and reconnects, there is nowhere for NATS to store the messages temporarily. You can solve this by storing messages in a stateful storage first, then use NATS as a way to distribute them. You would need your own mechanism to replay messages on reconnect. This is coincidentally what Jetstream does. It uses NATS internally as a network protocol, but it's a separate thing.

Re:High-Performance server for NATS.io, the cloud and edge n... by Kinrany on Monday July 24, 2023 @09:07AM (#36847361)
Jetstream is distributed as an optional part of NATS, so while it exists as a layer on top of NATS Core and provides a different model, describing NATS as entirely stateless is not totally accurate

Though I suspect that Synadia people might do at least one more minor iteration of Jetstream: it still seems a little more complex than it needs to be, unlike Core

Re:High-Performance server for NATS.io, the cloud and edge n... by rcombatwombat on Monday July 24, 2023 @06:50PM (#36855345)
Re:High-Performance server for NATS.io, the cloud and edge n... by gedw99 on Wednesday July 26, 2023 @04:37AM (#36874696)
what do you think of the new JetStream API ?