6 ms·
There are a couple of interesting options in a similar space: BedrockDB ( https://bedrockdb.com/ https://bedrockdb.com/ ) Dqlite ( https://dqlite.io/ https://dq
by splitrocket 4y ago
There are a couple of interesting options in a similar space:
BedrockDB ( https://bedrockdb.com/ https://bedrockdb.com/ )
Dqlite ( https://dqlite.io/ https://dqlite.io/ )
Rqlite ( https://github.com/rqlite/rqlite https://github.com/rqlite/rqlite )
I'm interested in how this performs and particularly, what are the tradeoffs relative to the other options above.
- benbjohnson 4y agoLitestream author here. The tl;dr is that Litestream trades operational complexity for reduced durability guarantees and increased write performance. Those 3 options mentioned use distributed consensus to ensure higher durability but that consensus also takes time so writes can be slowed. Litestream is an async replication tool so you can have a configurable window (1 second by default) where you could lose data if you have a catastrophic failure.