Redis Cluster
Redis Cluster is an open source, distributed in-memory data store for applications that need fast caching, session storage, or low-latency key-value access…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
71/100 Good
- Maintained
- 100last commit 4 days ago
- Popular
- 9877,711 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- 108 GB minimum RAM
Availability: platform listings confirmed today
- GitHub stars
- 77,711
- Open issues
- 3121
- Last commit
- 2026-11-17
- Latest release
- 8.10.3
- Activity
- rising
Checked 4 days ago - source: GitHub (redis/redis)
Resources & Compatibility
Minimum requirements: 8 GB RAM, 3 CPU core(s).
Checked 40 days ago - source: Docker Hub image tags and published docs
First-install notes
- Use hash tags for multi-key cluster commands When you run several keys together in a Redis Cluster command, put the same tag in braces in their names (for example, {myapp}:key1 and {myapp}:key2) so they are assigned to the same cluster slot. Without that, Redis may put the keys on different nodes and the multi-key operation fails. source
- Check which node a PubSub subscription uses PubSub (publish/subscribe messaging) connections in a cluster can be tied to a particular Redis node. If you need a channel handled by a specific node, choose that node when creating the connection; otherwise the client may connect to a different node than you expect. source
- Start the Redis + tracing example with Docker If you want the optional tracing demo, start it with Docker Compose (a tool that runs a group of containers from one file) using docker compose -f docs/examples/opentelemetry/docker-compose.yml up -d. That starts Redis and the tracing collector, with ports 4317 (gRPC) and 4318 (HTTP) carrying the tracing data, so make them reachable if you use them from outside. source
- Install Follow the Redis repository's Getting Started guide to install Redis and connect a client to the cluster. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives (10)
- Apache Cassandra
- CockroachDB - CockroachDB is a distributed SQL database for developers and operators of transactional applications that need horizontal scaling and resil…
- CouchDB - CouchDB is a document-oriented NoSQL database with a RESTful HTTP/JSON interface for storing, querying, and synchronising JSON documents ac…
- FerretDB - FerretDB is an open-source MongoDB compatibility proxy for self-hosted stacks.
- KeyDB - KeyDB is a distributed, Redis-compatible key-value database that adds true multi-master replication, letting any number of servers accept w…
- MongoDB - MongoDB is an open-source, document-oriented NoSQL database that stores flexible, JSON-like documents, helping developers and self-hosters…
- Valkey - Valkey is an open-source, high-performance in-memory key-value datastore forked from Redis.
- memcached - Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls,…
- ncache - NCache is a fast, scalable, open-source distributed cache for .NET applications that keeps frequently used data in a shared in-memory pool…
- rethinkdb - RethinkDB is an open-source, distributed NoSQL database built for realtime web applications.
Checked 40 days ago - source: AlternativeTo
Common questions
Why can multi-key Redis Cluster commands fail when keys are used together?
Keys in a multi-key cluster command need the same hash tag in braces, for example {myapp}:key1 and {myapp}:key2. That makes them map to the same cluster slot. Without it, Redis may put the keys on different nodes and the operation fails.
How can I control which Redis Cluster node handles a Pub/Sub subscription?
Pub/Sub connections in a cluster can be tied to a particular node. If a channel must be handled by a specific node, choose that node when creating the connection. Otherwise the client may connect to a different node.
Which ports need to be reachable if I run the optional Redis tracing example?
The Docker Compose tracing example uses port 4317 for gRPC and port 4318 for HTTP. Those ports carry tracing data, so make them reachable if you send traces from outside.
What Redis Software troubleshooting issues are called out for TLS problems?
The troubleshooting docs call out TLS failures, TLS connection failures caused by certificate expiration, and endpoint flapping.
Answers sourced from github.com, github.com, github.com, redis.io
Community
- Four ways to shoot yourself in the foot with Redis - Reddit (reddit)
- How can I handle redis-cluster with Redis Stack (RediSearch)? (forum)
Collected 48 days ago - public community threads