Building something that uses realtime features with liveview. There’s state that’s managed and pushed to call participants. Right now I’m using Cachex but if I do a deploy while someone is in a call, all the state will be lost? What’s the best way to have temporary in-memory storage that persists a…

Got no answer for you at the moment but why are you using an ephemeral state that can be lost at any time (cache) as a source of truth / database?

It’s not a source of truth really. It’s for temporary call/session data that doesn’t really make sense to store after the call finishes.

Depends on how you deploy. You can build a distributed cache that synchronizes agressively, and when you shut down a node to roll a new node, the stopping node stops accepting external input but will wait till all its currently processing cache items are synced on other nodes, and the new node will…

The route i would go is redis, memcached, or postgres. The alternatives are actually much more of a pain in comparison. They are quite fun though, so if your project needs a little pizzazz then read on. If you are running more than one node: GitHub - rabbitmq/khepri: Khepri is a tree-like replica…

@nerdyworm @lud Yeah thanks for the reality check guys. I think redis is ultimately what I’ll go with. Love the idea of having them replicated cluster-internally but don’t want to have to add persistent block storage or a volume mount to the app containers. Keep Cachex for read-through queries to t…

Elixir Programming Language Forum

Best options for Elixir-only persistent distributed cache?

Questions & Help Questions

Schultzer July 27, 2025, 1:20pm 4

Mnesia is the answer.