ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #redis
When utilizing the laminas-cache component with a Redis backend, latency spikes occur during high-concurrency invalidation events. While the adapter provides a unified interface for tagging, the implementation of clearByTag lacks inherent atomicity across distributed nodes. In a high-load environment, multiple processes may trigger tag-based invalidations si
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
When using Redis with the lazyfree-lazy-eviction option enabled, the server attempts to evict keys asynchronously to reduce latency spikes during memory pressure. The interaction of this setting with the allkeys-lru eviction policy is not fully documented, leaving administrators unsure whether asynchronous eviction provides the same latency guarantees as the
Least-Privilege Scope with Redis ACLs Redis 6.0 and later support Access Control Lists that restrict a user to specific key patterns with the ~ prefix alongside granular command permissions. When designing a least-privilege account, I want to confine an application user to a single namespace such as ~cache:* while still allowing ordinary read and write comma
Pagination Strategy for Large Datasets Implementing pagination for large datasets in Redis often involves a choice between rank-based indexing using ZRANGE and cursor-based iteration via ZSCAN . While ZRANGE allows for precise offset-based bounding, the underlying skip list traversal can lead to increased latency as the offset grows deeper into the set. Conv
Client Buffer Management in Pub/Sub Redis Pub/Sub follows a fire-and-forget model where messages are pushed to connected subscribers in real-time. Because these messages are not persisted, Redis manages the delivery via output buffers for each client. When a subscriber cannot consume messages as fast as the publisher produces them, the output buffer grows. T
Administrators want Redis to reject TLS connections when the client certificate does not match the hostname used to reach the server, ensuring that a certificate issued for one service cannot be reused for another. Currently, with tls-auth-clients set to yes, Redis validates the certificate chain and expiration but relies on the underlying OpenSSL library to
CodeIgniter 4 utilizes a driver-based caching system relying on Time-To-Live (TTL) for data expiration. While the framework supports various backends such as Redis, Memcached, and File, it lacks a native mechanism for tag-based invalidation or group cache clearing. When underlying database records are updated, the associated cache entries remain stale until
Goal: achieve the lowest possible write latency in Redis while maintaining a durability level that tolerates at most a few seconds of data loss. Understanding the trade‑off is complicated because the latency impact of RDB, AOF, and the hybrid mode varies with the fsync policy (always, everysec, no) and with how often background rewrites are triggered. Which
laminas
codeigniter
php