←back to thread

Show HN: FeOx – Fast embedded KV store in Rust

(github.com)
37 points mehrant | 1 comments | 22 Aug 25 07:57 UTC | HN request time: 0.201s | source
Show context
emschwartz ◴[22 Aug 25 11:53 UTC] No.44983394[source]▶
Sounds interesting, though that durability tradeoff is not one that I’d think most people/applications want to make. When you save something to the DB, you generally want that to mean it’s been durably stored.

Are there specific applications you’re targeting where latency matters more than durability?

replies(3): >>44983526 #>>44985613 #>>44989509 #
1. digikata ◴[22 Aug 25 20:36 UTC] No.44989509[source]▶
This seems around the durability that most databases can reach. Aside from more specialized hardware arrangements, with a single computer, embedded database there is always a window of data loss. The durability expectation is that some in-flight window of data will be lost, but on restart, it should recover to a consistent state of the last settled operation if at all possible.

A related questions is if the code base is mature enough when configured for higher durability to work as intended. Even with Rust, there needs to be some hard systems testing and it's often not just a matter of sprinkling flushes around. Further optimization can try to close the window tighter - maybe with a transaction log, but then you obviously trade some speed for it.