NATS by itself is designed to be more of an always-on style queuing system (the ...

		jonathanoliver on May 22, 2020 \| parent \| context \| favorite \| on: An introduction to RabbitMQ NATS by itself is designed to be more of an always-on style queuing system (the term they use is "dial tone") but doesn't handle node failures by itself. If you're looking for a Kafka-flavored NATS, there's a new release I saw recently called LiftBridge that adds some durability to the NATS protocol.

Someone mentioned this already below, but nats streaming also adds durability.