Why keep buying servers for RAM? Lavik combines NVMe SSD capacity with throughput above Redis on DRAM. Explore the architecture, benchmarks & economics of a 300-to-3 consolidation.
Do you mean the use case of a 300-node Redis Cluster?
It’s very common. Since Redis typically runs with 2 vCores per node, a 300-node cluster can only store about 2.4 TB of data.
It’s common in human-centric feature stores and profile stores. But it’s even more common in agent profile stores, since agent profiles are a much larger category.
The three node setup doesn't make sense to me. Why not offer a user-selectable RAID-like choice instead (or even no redundancy)? Also, I don't like the idea of having any node labeled as Primary.
16 comments
[ 2.9 ms ] story [ 38.6 ms ] threadIt’s very common. Since Redis typically runs with 2 vCores per node, a 300-node cluster can only store about 2.4 TB of data.
It’s common in human-centric feature stores and profile stores. But it’s even more common in agent profile stores, since agent profiles are a much larger category.
Haven't seen anything more "hyperscaler-brained" in a while.
https://lavik.dev/en/compare/lavik-vs-dragonfly/