Valkey in Telecom: Leveraging Open Source for Unique Needs and G...
summary
Ericsson describes adopting Valkey (a fast Redis fork) inside 5G core stacks, handling millions of requests per second using a clustered, sharded architecture with in‑process caches and pipelined single‑connection routing. Engineering adds dual-channel replication (separate snapshot + change stream), IO offload threads, a compact cache-line bucket hash to cut memory, and a supported downgrade during rolling upgrade path so operators can revert safely. The setup runs in Kubernetes and is production‑validated.
AI-written summary · about
chapters (15)
- 0:00Valkey in Telecom intro
- 1:05What is Valkey
- 3:52Ericsson mobile networks
- 6:43Ericsson’s Valkey switch
- 10:59Valkey in 5G core
- 11:43Telecom needs for Valkey
- 16:41Valkey in mobile networks
- 17:24Valkey cluster setup
- 19:31In-process cache fallback
- 20:15Valkey 8.0 and 8.1 features
- 23:09Dual channel replication
- 24:30Performance optimizations
- 26:36Hash table optimizations
- 30:51Call to action
- 31:37Q&A
related talks
34mTwo Hard Things: Naming Things & Cache Invalidation, Valkey Edition
48mWhat's New in Valkey 9?
25mYou Never Know When You Need a Fork
23mKeynote: 5G as Platform for Innovation and the Role of Open Source in the 5G Network Evolution
32mYou Never Know When You Need a Fork: Lessons Learned Building...
24mKeynote: An Open Approach: Virtualizing the CO for Mobile Services
23mKeynote: Bring Disruptive Innovation to Deployment with Curated Open Source
05mKeynote: The Path To Innovation is Open Source for Telecommunications Service Providers