Atomic Multi‑Key Operations in Redis with Lua Scripting (EVAL)
Learn how Redis Lua scripts let you perform multiple key updates atomically in a single round‑trip, with a step‑by‑step example, limits, and common pitfalls to avoid.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Redis Lua scripts let you perform multiple key updates atomically in a single round‑trip, with a step‑by‑step example, limits, and common pitfalls to avoid.
Learn how to implement real-time updates in Rails using Action Cable and Redis to synchronize data across multiple server processes.
Stop broadcasting to every client. Learn how to use Socket.IO rooms to target specific groups of users and how to scale that logic using the Redis adapter.
Learn how to choose between Memory, Filesystem, and Redis adapters in Zend/Laminas to optimize performance and avoid cache fragmentation in distributed environments.
Explore how Twitter's fan-out architecture optimizes read latency by shifting the computational burden from the reader to the writer, and how a hybrid model handles the 'celebrity' scale problem.
Design a distributed semaphore using Redis and Lua scripts to enforce a global concurrency limit across microservices. The article covers requirements, minimal design, trust boundaries, operational checks, failure modes, and when to adjust the architecture.
Learn how to use Redis Pub/Sub for real-time signaling. Understand the fire-and-forget mechanism, the subscriber state, and why it differs from message queues.
Goal: Choose a Redis client library that reliably handles burst request rates while enforcing a fixed max‑total connection limit. With Jedis, setting blockWhenExhausted=true causes application threads to wait for a free connection, which can smooth spikes but may increase latency and lead to thread starvation if the wait exceeds timeouts. Lettuce shares a si
Doctrine ORM implements a second-level cache (SLC) to reduce database load. To prevent cache stampedes, the system employs a locking mechanism when multiple concurrent requests encounter a cache miss for the same entity. This mechanism relies on the underlying cache adapter's atomic operations, such as the SET NX EX command when using a Redis backend. Under