3 ms·

NATS data is ephemeral in many cases anyhow, so it makes a bit more sense here. If you wanted something fully durable with a stronger persistence story you'd pr

NATS data is ephemeral in many cases anyhow, so it makes a bit more sense here. If you wanted something fully durable with a stronger persistence story you'd probably use Kafka anyhow.

nchmy 11mo ago
Core nats is ephemeral. Jetstream is meant to be persisted, and presented as a replacement for kafka
petre 11mo ago
So is MQTT, why bother with NATS then?
- KaiserPro 11mo ago
  MQTT doesn't have the same semantics. https://docs.nats.io/nats-concepts/core-nats/reqreply https://docs.nats.io/nats-concepts/core-nats/reqreply request reply is really useful if you need low latency, but reasonably efficient queuing. (making sure to mark your workers as busy when processing otherwise you get latency spikes. )
  - RedShift1 11mo ago
    You can do request/reply with MQTT too, you just have to implement more bits yourself, whilst NATS has a nice API that abstracts that away for you.
    - KaiserPro 11mo ago
      oh indeed, and clusters nicely.
traceroute66 11mo ago
> NATS data is ephemeral in many cases anyhow, so it makes a bit more sense here Dude ... the guy was testing JetStream. Which, I quote from the first phrase from the first paragraph on the NATS website: NATS has a built-in persistence engine called JetStream which enables messages to be stored and replayed at a later time.