Why? Why do some databases do that? To have better performance in benchmarks? It’s not like that it’s ok to do that if you have a better default or at least write a lot about it. But especially when you run stuff in a small cluster you get bitten by stuff like that.
Yes, exactly.
- ACKed messages can be silently lost due to minority-node corruption.
- Single-bit corruption can erase up to 78% of stored messages on some replicas.
- Snapshot corruption may trigger full-stream deletion across the cluster.
- Default lazy-fsync wipes minutes of acknowledged writes on crash.
- Crash + delay can produce persistent split-brain and divergent logs
Are you the Mother? Because only a Mother could love such a ugly baby....
as they would say, NATS is a terrible message bus system, but all the others are worse
vrnvu•49m ago
https://jepsen.io/blog/2025-10-20-distsys-glossary