Getting distributed with Firenest
summary
Firenest assembles concrete building blocks for distributed Elixir: a pluggable topology layer (distributed Erlang, Redis parity, or Partisan later), a tiny in-node pubsub implemented with Registry, a sync-server abstraction for named processes, and a replicated state store that ships incremental deltas for ephemeral per-process data (presence, rate limits, caches). It avoids heavy CRDTs for ephemeral keys, claims simpler correctness and performance, offers a VM-local test topology to simulate many nodes, and remains an active research prototype not yet production-ready.
AI-written summary · about
chapters (7)
- 0:00Introduction to Firenest
- 3:34The distributed systems gap
- 8:14Phoenix presence and vision
- 12:23Core Firenest components
- 17:39Sync server and state
- 22:17API and implementation
- 26:00Future goals and conclusion
related talks
33mDiscovering distributed systems in Elixir
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
39mAn adventure in distributed programming
36mKnee Deep Into P2P
41mIdioms for building fault-tolerant applications with Elixir
57mReliability Nirvana
23mCracking the PubSub Code. Elixir's Key to Scalable Real-Time Systems
46mPartisan: high performance large scale distributed Erlang