What it comes down to is performance. You can use a relational database such as SQLite for a low-level key-value store, such as RocksDB or SplinterDB, but then you pay for the higher-level semantics with lower…
With many workloads, there's a tradeoff between the granularity of durability and the overall performance. If a workload has many small writes (some of our product workloads do), then syncing each write can cause write…
Hi, research lead for SplinterDB here. SplinterDB does make all writes durable and in fact has its own user-level cache which generally performs writes directly to disk (using O_DIRECT for example). Like RocksDB's…
What it comes down to is performance. You can use a relational database such as SQLite for a low-level key-value store, such as RocksDB or SplinterDB, but then you pay for the higher-level semantics with lower…
With many workloads, there's a tradeoff between the granularity of durability and the overall performance. If a workload has many small writes (some of our product workloads do), then syncing each write can cause write…
Hi, research lead for SplinterDB here. SplinterDB does make all writes durable and in fact has its own user-level cache which generally performs writes directly to disk (using O_DIRECT for example). Like RocksDB's…