# Valkey-cluster

Valkey-cluster is the Bitnami Helm chart for deploying Valkey, the open-source in-memory key-value store forked from Redis, in cluster mode. It is open source and self-hosted, installable on Docker Hub, Proxmox and Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/6393/valkey-cluster

## Description

Valkey-cluster is the Bitnami Helm chart for deploying Valkey, the open-source in-memory key-value store forked from Redis, in cluster mode. It shards data across multiple nodes with replication and automatic failover, giving self-hosters a fast, highly available cache or data store for traffic-heavy applications.

## Platform availability

Available on 2 of 10 platforms: Proxmox, Helm.

## Health score

82/100 (Excellent), based on 4 of 4 factors.
- Maintained: 100 (last commit 16 days ago)
- Popular: 89 (27,626 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 85 (512 MB minimum RAM)

## Links

- Docker Hub: https://hub.docker.com/r/bitnamicharts/valkey-cluster
- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=valkey
- Official website: https://valkey.io
- GitHub: https://github.com/valkey-io/valkey
- Kubernetes (Helm): https://artifacthub.io/packages/helm/bitnami/valkey-cluster

## Common questions

### How can I check that my app is reaching the right Valkey node and port?

Point the app to the Valkey node host and port you configured, often localhost:6379. Then send PING and expect PONG to confirm the host, port, and network connection work.

### Can Valkey Cluster be used for a production deployment?

The Valkey Cluster documentation explains how to set up, test, and operate Valkey Cluster in production. It also covers availability and consistency characteristics from the end user's point of view.

### Should I store large binary blobs in Valkey?

A common design pattern is to keep write-heavy small data in Valkey and store big blobs in an SQL or eventually consistent on-disk database.

### Can Valkey be used as a cache and queue for self-hosted Langfuse?

Yes, Valkey can be configured as the caching layer and queue for self-hosted Langfuse. The guidance covers Redis environment variables, connection options, and configuration best practices.

## Alternatives

- 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…
- 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…
- Redis: Redis is a fast, in-memory data structure store that can be used as a database, cache, and message broker.
- 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6393/valkey-cluster), the self-hosted and open-source app directory.
