Settings

Theme

Migrate Your 300-Node Redis Cluster to Just 3 Lavik Nodes

lavik.dev

18 points by hubertzhang · 16 comments

Reader

6 threads
stephbook

Does anyone read websites like these? AI scrapers maybe?

  • hubertzhangOP

    I'm the author... Codex is co-author but the blog “Migrate Your 300-Node Redis Cluster to Just 3 Lavik Nodes” is reviewed by myself.

stuaxo

What on earth is running on that, Panantirs spying database ?

  • hubertzhangOP

    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.

    • CAP_NET_ADMIN

      > 2 vCores per node, a 300-node cluster can only store about 2.4 TB of data.

      Haven't seen anything more "hyperscaler-brained" in a while.

    • timcobb

      what is anagent profile store that is deployed at the scale of terabytes? Do you mean, for example, logs of agent sessions that run on providers?

dotnwat

Do you have comparisons against Dragonfly?

jacquesm

I swear I've seen this link a couple of days ago.

throw20261022

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.

throw20261022

GitHub link: https://github.com/eloqdata/lavik

Keyboard Shortcuts

j
Next item
k
Previous item
o / Enter
Open selected item
?
Show this help
Esc
Close modal / clear selection