An Introduction to Messaging in Valkey
summary
Valkey is an open BSD key‑value datastore backed by the Linux Foundation and forked from Redis, claiming 1M ops/sec on one box and scale to ~1B ops/sec across 2,000 nodes. Messaging is built from primitives: lists with blocking LPUSH/BLPOP and atomic RPOPLPUSH for safe work queues, sorted sets for priority queues, and streams with consumer groups, XCLAIM/XACK plus Lua transactions. Demo ties Valkey to Celery as broker+backend, uses Redis 7.2.4 compatibility, and shows notifications working end‑to‑end.
AI-written summary · about
chapters (15)
- 0:00Valkey introduction
- 1:07What is Valkey
- 2:31In-memory messaging
- 3:36Fire-and-forget channels
- 4:39Queues with lists
- 6:47Atomic list operations
- 7:50Priority queues
- 11:01Streams for messaging
- 13:51Consumer groups
- 15:14Celery use case
- 18:42Demo setup
- 21:11Flight delay demo
- 23:17Demo results
- 24:44Time-to-live for keys in Valkey
- 26:34Summary
related talks
33mDiscover Valkey: The Path to Now
45mDemystifying Valkey Clustering: Architecture, Fault Tolerance, and Scalability
48mValkey clusters unboxed
44mCustomizing Valkey with Rust: Building High-Performance Modules
44mValkey: Latency in Cloud Environments
36mWhat’s New in Valkey
41mValkey 8 — Release of a Redis Fork Focused on Performance
14mMigrating 15k Redis servers to Valkey