Valkey

The managed Valkey service — a Redis-compatible in-memory datastore. Topologies, eviction policies, persistence, backups and external access.

6 articles

• Valkey

  Bahriya provides managed Valkey instances — an in-memory datastore for caching, sessions, queues, counters, pub/sub and real-time data, deployed alongside your containers and managed from the same console, CLI and Terraform provider as everything else.

  3 min

• Topologies

  The tier decides how many nodes an instance runs, what happens when one fails, and — the one product fact that reaches your code — which client driver your application needs. Pick the smallest tier that meets your availability and capacity requirements.

  3 min

• Connecting to Valkey

  Any Redis-compatible client library connects to Valkey unchanged — the wire protocol, commands and authentication are the same. What varies by tier is how the driver should be configured.

  2 min

• Eviction policies

  An instance has a fixed amount of memory. The eviction policy answers one question: *when memory is full and a write arrives, what gives way?* This page explains each policy in the console's Eviction Policy dropdown and when to choose it.

  3 min

• External access

  By default a Valkey instance is reachable only by containers in its own project. You can additionally expose it at the platform edge — for an application hosted elsewhere, a data pipeline, or a migration — on the standard port 6379.

  3 min

• Persistence and backups

  Durability on Valkey is a property of the instance's purpose, set at creation:

  2 min