I'm talking about the backend for storing the messages/events in the outbox pattern. That's how to persist in case of a network failure. The outbox-pattern pa

I'm talking about the backend for storing the messages/events in the outbox pattern. That's how to persist in case of a network failure. The outbox-pattern pattern removes the send message from it's datastore when send/acknowledged. Persistency is different from the outbox-pattern, it handles what is does if the message broker received the message. The outbox pattern handles failure before the message reached the message broker. NoSql and event stores normally have methods to adjust data to the latest version of the model, eg. Postgress ( which can be used as NoSql using bson) supports js v8 transformations. This is useful for edge-cases in the outbox pattern. In short, I was more or less talking about the tech used. Rabbit vs Nats and sqllite vs NoSql ( in my case, using Postgress as NoSql). Ps. Nats can be persistent as others mentioned in this thread, look up: nats streaming