When is Redis a good fit?
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
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
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
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
Application performance is one of the main reason of using cache over relational database. Because it stores data in memory in the form of key value pair, we can store frequently accessed data in cache which are not changes very frequently. Reading from cache is much faster than database. Redis is one of the best solution in distributed cache market. I was d
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
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Recently, we had an outage due to Redis being unable to write to a file system (not sure why it's Amazon EFS) anyway I noted that there was no actual HEALTHCHECK set up for the Docker service to make sure it is running correctly, Redis is up so I can't simply use nc -z to check if the port is open. Is there a command I can execute in the redis:6-alpine (or n