Enter EloqKV: a Redis-protocol-backed store that adds durability without turning DBs into a spaghetti stack. The pitch is blunt: fewer moving parts can win—when the workload fits—against traditional databases like Postgres and Redis. [1]
Architecture snapshot — At its core, EloqKV uses the Redis protocol but adds a redo log, enabling multi-writer transactions, persistence, durability, and stored procedures. [1]
Fewer moving parts in practice — That ethos shows up as one engine handling database and cache roles, potentially shrinking failure domains and maintenance tasks. [1]
Performance and comparisons — In tests, EloqKV is faster than KVRocks, especially for in-memory reads, and it can scale to multiple nodes. It also outperforms TiKV in some in-memory workloads. [1]
Reliability and maintenance — EloqKV emphasizes durability by default through persistence and a redo log, with multi-writer support and transactions. It’s open source under a GPL license. [1]
Closing thought: the real test is how this approach holds up in real deployments and benchmarks as it matures. [1]
References
Postgres is reliable – I'll persist in EloqKV
EloqKV blends Redis protocol with durability; compares to Redis, TiKV, KVRocks, and Postgres; argues fewer moving parts help.
View source