4 ms·
> How does it compare to NATS.io? They're fundamentally different designs. Garden variety NATS (i.e. the non-"Jetstream" case, hereafter) is "at most once" (m
by topspin 3y ago
> How does it compare to NATS.io?
They're fundamentally different designs.
Garden variety NATS (i.e. the non-"Jetstream" case, hereafter) is "at most once" (messages will be lost.) BlazingMQ is "at least once" (>1 delivery of a message will occur.)
That difference is down persistence. NATS doesn't persist messages to stable storage. BlazingMQ must use persistent storage. From that all sorts of application design, performance and other implications are derived. And they all matter. A lot.