Redis
The most recommended of 6 in-memory data stores
A fast, simple, battle-tested in-memory store with rich data structures, popular for caching and cross-node coordination; critics call it overused and warn about durability and licensing changes.
A fast, simple, battle-tested in-memory store with rich data structures, popular for caching and cross-node coordination; critics call it overused and warn about durability and licensing changes.
276 people gave an opinion
- recommend it
- 174
- criticize it
- 102
- approval share
- 63%
Recommended in 12 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 10 years
Median of the 7 owners who said how long they have had it.
Each square is one year.
Why it doesn’t carry the badge
- 174 people recommend itNeeds 10 or more, met.
- 1.7 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 12 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Very fast in-memory performance
“Key-value operations are mostly O(1). You'll never get that kind of performance with other databases because they intentionally don't give you that granularity.”
Comment from 17 Jan 2026 in “JuiceFS is a distributed POSIX file system built on top of Redis and S3” “The point of Redis is that it is in memory and you can smash it with hot path queries while taking a lot of load off the backing DB.”
Comment from 5 Feb 2026 in “It's 2026, Just Use Postgres” “It's a 10 lines Python script that will deliver 20k/50k queries per second more or less, out of the box with zero optimizations.”
Comment from 7 Mar 2026 in “Querying 3B Vectors” - Comment from 6 Jul 2026 in “You probably don't need another database”
- Comment from 23 Jun 2026 in “In Praise of Memcached”
- Comment from 6 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements”
Rich, battle-tested data structures
“Redis gives you a very well-defined/understood set of rich data structures with built-in behavior like TTL, atomic operations, eviction, and persistence.”
Comment from 5 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements” “if Redis was embeddable you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more”
Comment from 5 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements” “Redis uses a skiplist for range queries and ordered iteration paired with a hash table for O(1) lookups”
Comment from 19 Apr 2026 in “What Are Skiplists Good For?” - Comment from 26 Feb 2026 in “You Just Need Postgres”
- Comment from 13 May 2026 in “Redis and the Cost of Ambition”
Easy to set up and run
“Redis is brought into a stack because (most importantly!) it's fast and (almost as importantly!) because it's simple.”
Comment from 23 Jun 2026 in “In Praise of Memcached” “Throwing a hosted Redis in front of some hot-path API calls is very straightforward and easier to reason about”
Comment from 24 Jun 2026 in “PostgreSQL Is Enough” “Redis/Valkey is relatively easy to stand up... I almost don't give it a second thought to stand up Redis”
Comment from 13 May 2026 in “Redis and the Cost of Ambition” - Comment from 6 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements”
Shared coordination across many nodes
“The entire value of redis IMO is that is ISN'T inside your normal application, but rather some shared storage that all nodes can use to coordinate”
Comment from 5 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements” “redis gives you more goodies. You can store temporary state for tasks that require coordination between multiple nodes without race conditions”
Comment from 28 Jan 2026 in “Oban, the job processing framework from Elixir, has come to Python” “having Redis able to handle scale independently of postgres has been a life saver, and saved us a lot of money”
Comment from 27 Feb 2026 in “You Just Need Postgres”
What people warn about
Each mark is one comment
Overused, adds needless complexity
“The idea of a separate networked process to store and retrieve variables from memory sounds like something a first year engineer would do”
Comment from 13 Jul 2026 in “Control the Ideas, Not the Code” “seeing startups spin up managed postgres + redis clusters + prisma on day 1 just to collect waitlist emails is peak feature vomit”
Comment from 15 Apr 2026 in “Do You Even Need a Database?” “The amount of redis-as-database, or X really, that I see deployed that practically make no sense is insane.”
Comment from 25 Jun 2026 in “PostgreSQL Is Enough” - Comment from 6 Dec 2025 in “100k TPS over a billion rows: the unreasonable effectiveness of SQLite”
Can lose data, weak consistency
“It should not land in broken states so easily. It should not limit the number of writers. It should not error during failover.”
Comment from 5 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements” “most competent programmers decided that redis was just a smarter memcache and started designing around data loss”
Comment from 7 Oct 2026 in “From the creator of Redis; run LLM locally with ds4” “The docs explicitly state that clusters do not provide strong consistency and can lose acknowledged data.”
Comment from 9 Dec 2025 in “Jepsen: NATS 2.12.1” Source-available license change backlash
“They cared more about making money and open source was a useful facade to get people to contribute for free.”
Comment from 11 May 2026 in “I returned to AWS, and was reminded why I left” “all these hipsters startups (MongoDB, Redis, etc) all ended up enshittifying their open source products”
Comment from 12 Jan 2026 in “MIT Non-AI License” “That's why we had huge backlash when Redis, Elasticsearch, and Terraform went source-available, right?”
Comment from 29 Oct 2026 in “We're releasing the weights of Mistral Large 4” Narrow workloads, no indexes
“Redis does not support indexes and all sorts of other things. It works well only for a specific kind of workload”
Comment from 8 Jun 2026 in “Do we fear the serializable isolation level more than we fear subtle bugs?” “Redis works great as a cache, but there are a few things you need to do in order to use it reliably as a cache.”
Comment from 23 Jun 2026 in “In Praise of Memcached”
Other in-memory data stores people recommend
The four most recommended other in-memory data stores, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| RedisThis page | 174 | 102 | 63% | 12 | 10 yrs7 owners | — |
| Valkey | 31 | 5 | 86% | 10 | — | Approved |
| Memcached | 27 | 10 | 73% | 6 | — | Approved |
| Lux Redis-compatible server | 8 | 7 | 53% | 2 | — | — |
| KiviDB | 7 | 2 | 78% | 1 | — | — |
What people said
40 of the 332 comments that mention it, newest first. Each links to the original comment.
“That's why we had huge backlash when Redis, Elasticsearch, and Terraform went source-available, right?”
“most competent programmers decided that redis was just a smarter memcache and started designing around data loss”
“Redis is still a mainstay of many companies and in ~30% of the cases I review I find one or more installations.”
“Redis has great qualities, I don't use it often but I've also for years now understood why Redis was put in front of these use cases”
“I really just disagreed with the assessment that redis is not good enough for the job for a reservation system”
“The idea of a separate networked process to store and retrieve variables from memory sounds like something a first year engineer would do”
“Low memory, high-performance, feature-rich, and stable. Really hard to beat it for places where you want a durable cache”
“The amount of redis-as-database, or X really, that I see deployed that practically make no sense is insane.”
“Throwing a hosted Redis in front of some hot-path API calls is very straightforward and easier to reason about”
“having hybrid solutions like Redis and their flash memory solution is probably going to be the compromise going forward”
“redis is more a arbitrary shared Python heap kinda thing with all the data structures and single thread”
“Redis is brought into a stack because (most importantly!) it's fast and (almost as importantly!) because it's simple.”
“Redis works great as a cache, but there are a few things you need to do in order to use it reliably as a cache.”
“Redis does not support indexes and all sorts of other things. It works well only for a specific kind of workload”
“it's really (and i mean really) fast, very easy to get up and running and the protocol is pretty simple”
“The entire value of redis IMO is that is ISN'T inside your normal application, but rather some shared storage that all nodes can use to coordinate”
“if Redis was embeddable you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more”
“Redis is a real database. If I wasn't convinced it could retain data I hand it, I wouldn't use it in the first place.”
“It should not land in broken states so easily. It should not limit the number of writers. It should not error during failover.”
“Redis gives you a very well-defined/understood set of rich data structures with built-in behavior like TTL, atomic operations, eviction, and persistence.”
“For simple cases, it is probably a total overkill to even consider it, but for something heavier, embedding the database gives you a chance to trivially migrate later”
“directly use Redis as it was intended (data structures over the network) then it makes sense”
“Redis/Valkey is relatively easy to stand up... I almost don't give it a second thought to stand up Redis”
“They cared more about making money and open source was a useful facade to get people to contribute for free.”
“Redis uses a skiplist for range queries and ordered iteration paired with a hash table for O(1) lookups”
“seeing startups spin up managed postgres + redis clusters + prisma on day 1 just to collect waitlist emails is peak feature vomit”
“It's a 10 lines Python script that will deliver 20k/50k queries per second more or less, out of the box with zero optimizations.”
“we had to switch to redis for another sub-system and IIRC there some positive implication for cache layer as well”
“having Redis able to handle scale independently of postgres has been a life saver, and saved us a lot of money”
“Redis has a bunch of algorithms which are battle-tested and ease implementation of common patterns.”
“The point of Redis is that it is in memory and you can smash it with hot path queries while taking a lot of load off the backing DB.”
“many developers don't mind using Docker to run Redis / Postgresql and other services on Mac that are very simple to install and run directly”
“redis gives you more goodies. You can store temporary state for tasks that require coordination between multiple nodes without race conditions”
“Key-value operations are mostly O(1). You'll never get that kind of performance with other databases because they intentionally don't give you that granularity.”
“Redis is as reliable as the storage you persist it to. If you're running Redis right, it's very reliable.”
“this is why redis was preferred anyways: it was a lightweight database for the task processor to store state, etc.”
“all these hipsters startups (MongoDB, Redis, etc) all ended up enshittifying their open source products”
“The docs explicitly state that clusters do not provide strong consistency and can lose acknowledged data.”
“they go with microservices, Redis, RabbitMQ, etc, making the system more complex and less available”
“Mature C programs written by professional coders (Redis is a good example) basically never crash in the experience of users.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.