Free audit

View Audit Scope
ValkeyRemote DBA, support, and scoped projects

Valkey database services for production teams.

JusDB provides Valkey database services for scoped projects, ongoing remote DBA coverage, production support, performance tuning, moves from Redis, cluster design, and high availability. We work across Amazon ElastiCache, Amazon MemoryDB, Google Cloud Memorystore, Kubernetes, and your own servers. 24x7 on-call is available under your service agreement.

Or request a free audit of one database instance. Already in an incident? See Valkey support.

  • NDA before access
  • Read-only by default
  • Changes measured against your baseline

Valkey version status

Pick the version you run

Valkey 9.1

Newest stable

First released on 19 May 2026, with bug fixes until May 2029. Security fixes are listed until May 2031, the longer window Valkey gives the latest minor version of each major version.

Valkey 9.1 adds an availability-zone field to CLUSTER SHARDS and CLUSTER SLOTS replies, which some strict cluster clients may reject.

Check cluster clients

Version status from the Valkey releases page, the Valkey migration guide, and the Amazon ElastiCache notes for Valkey, checked 28 October 2026.

Platforms
Amazon ElastiCache and MemoryDB, Google Cloud Memorystore, your own servers, and Kubernetes
High availability
Valkey Sentinel, Valkey Cluster, ElastiCache Multi-AZ, and MemoryDB
Incidents
Initial-response targets are set in your service agreement. See the targets

Symptoms

Eight Valkey problems we are asked to fix

Each one has a cause we can measure. The scoping call starts from the symptom you see, the Valkey version, and where it runs.

  1. A Redis 7.4 or Redis 8 snapshot will not load into Valkey because Valkey reads Redis data files only up to Redis OSS 7.2.

  2. ElastiCache clusters still run Redis OSS 4, 5, or 6 even though 4 and 5 moved to paid Extended Support in February 2026, and 6 follows in February 2027.

  3. An application that uses SELECT breaks in cluster mode because cluster mode served only database 0 before Valkey 9.0, and cluster-databases still defaults to 1.

  4. Keys with a TTL vanish early on ElastiCache because the default parameter group sets maxmemory-policy to volatile-lru, which can evict them under memory pressure.

  5. A full resync drives up memory on the primary because it buffers new writes for the replica during the transfer. Dual-channel replication, available from Valkey 8.0 but off by default, moves that buffer to the replica.

  6. More io-threads did not fix a slow command because I/O threads handle client traffic, while commands still run one at a time on the main thread.

  7. One shard runs hot while the others sit idle because hot or large keys sit in that primary's slots, which CLUSTER SLOT-STATS, from Valkey 8.0, can reveal.

  8. Resharding causes latency spikes on large keys because legacy slot migration moves each key with MIGRATE, which blocks both nodes during the transfer.

If one of these is costing your team time, a scoping call is the place to start.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Failover

How a network partition can lose acknowledged Valkey writes

Valkey replicates asynchronously, so a primary confirms a write without waiting for any replica. If a partition isolates a primary beyond cluster-node-timeout, the majority promotes a replica, and the isolated primary's writes can be lost.

One cluster shard, three outcomes

Choose a state to see where the writes go.

Clients and routing

Cluster-aware clients send each key to the primary that owns its hash slot.

Writes on the primary
  • Primary

    Replies to writes without waiting for replicas

    Healthy

  • Replica 1

    Reports its replication offset every second

    Current

  • Replica 2

    A little behind during write bursts

    Slightly behind

For a moment after each write, the newest data can exist on the primary only.

We decide per workload how much write loss is acceptable, because a session cache and a payment queue need different answers. We set min-replicas-to-write and cluster-node-timeout to match, and use WAIT where a write needs a replica copy first. We alert on replica lag and full resyncs.

We rehearse failover on a copy with CLUSTER FAILOVER, or test-failover on ElastiCache, before production depends on it. Where an acknowledged write must survive a failover, we assess Amazon MemoryDB and ElastiCache synchronous durability (Valkey 9.0 and later). AWS documents both as logging each write across Availability Zones before confirming it.

What we cover

Full-spectrum Valkey engineering

From one hot key to a move off Redis OSS: INFO, COMMANDLOG, the latency monitor, and per-slot statistics drive every change.

  • Cluster setup

    Shard count, replica placement, and slot layout, sized from your data and write load.

    • Hash tags for keys that must share a slot
    • Replicas placed in separate failure zones
    • Atomic slot migration on Valkey 9.0 and later
    Valkey Cluster design
  • Moving from Redis

    Moves from Redis OSS 7.2 and earlier by replication or snapshot, with a rollback plan.

    • Valkey replicas of your Redis primary, promoted at cutover
    • Clients, scripts, and modules checked first
    • In-place upgrades from ElastiCache (Redis OSS)
    Redis to Valkey migration
  • Performance optimization

    We find what blocks the main thread first, and measure each change against your baseline.

    • COMMANDLOG or SLOWLOG, and the latency monitor
    • Big and hot keys found with valkey-cli
    • io-threads sized to the spare cores
    Valkey performance tuning
  • High availability

    Failover planned around the data loss and downtime you can accept (RPO and RTO), then rehearsed.

    • At least three Sentinels in separate failure zones
    • min-replicas-to-write to limit the loss window
    • Manual failovers with SENTINEL FAILOVER or CLUSTER FAILOVER
    Valkey high availability
  • Data persistence

    RDB snapshots, the append-only file (AOF), or both, chosen for how much data you can lose.

    • appendfsync everysec, which can lose about a second of writes
    • Fork time checked with latest_fork_usec
    • Restores tested on a copy
  • Monitoring and alerting

    Dashboards and alerts on the metrics Valkey exposes, so each alert points to a cause.

    • Prometheus and Grafana with redis_exporter
    • Alerts on memory headroom, evictions, and replica lag
    • Per-slot CPU and network with cluster-slot-stats-enabled
    Valkey remote DBA

Incident support

A critical (P1) page, answered within your agreement's target

JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.

Initial-response targets

  • 2 to 4 hours

    Business hours

    During covered business hours

  • 15 minutes

    24x7 on-call

    P1 incidents

P1 · Critical15 minutes

Production database down, primary unreachable, data corruption risk, or active failover event.

P2 · High30 minutes

Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.

P3 · Medium60 minutes

Non-critical slow query regression, staging issue, backup warning, or replication check alert.

P4 · Low90 minutes

Configuration question, index advisory, planned schema review, or general operational request.

Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.

Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.

What happens on a P1 page

  1. Page

    You page the on-call engineer

    Through the escalation path your service agreement names.

  2. Triage

    Root cause from INFO, COMMANDLOG, and per-slot statistics

    Hot slots, slow commands, memory pressure, and replica resyncs traced to the key or setting behind them.

  3. Mitigate

    Stabilize first, from the runbook

    Kill the blocking script or client, or fail over to a current replica, then fix the cause once production is steady.

  4. After

    A review after every P1

    What happened, why, and the change that stops it happening again.

Before and between incidents

  • Your setup, written down firstDuring onboarding we record your versions, shards, Sentinel or cluster layout, persistence, and eviction settings, so incidents start with context.
  • One escalation path, in writingYour service agreement names the on-call contact, the hours, and the Valkey deployments covered.
  • Reviews between incidentsWe review latency, memory headroom, slot balance, replication, and restores, and report open risks with next steps.
  • Version dates trackedWe track Valkey and ElastiCache support dates for the versions you run, and plan upgrades before fixes stop.

Process

How a Valkey engagement runs, step by step

Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.

  1. Scoping call

    Your Valkey deployments, versions, platforms, and what you need covered.

  2. Read-only review under NDA

    Our engineers use named ACL users with only the permissions the review needs, then read your configuration, INFO, COMMANDLOG, latency history, Sentinel or cluster state, and CloudWatch on AWS.

  3. A written report before any change

    Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).

  4. Changes, then handover

    We rehearse risky changes on a replica or a copy, apply them in the windows you approve, measure them against the baseline, and hand over updated operating instructions (runbooks).

Ways to work

Choose the Valkey service your team needs

Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.

Where your Valkey runs, and the tools around it

Your team and ours

What a managed Valkey service still leaves to your team

Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.

Who handles each part of running Valkey on a managed cloud service and on your own servers
QuestionManaged cloud serviceYour own servers or Kubernetes
Nodes, patches, and replacementsThe provider runs them.Your team, or JusDB under your agreement.
FailoverThe provider runs it. Your clients still have to follow the new primary.You run Valkey Sentinel or Valkey Cluster, with write limits that narrow the loss window.
Acknowledged writes in a failoverCan be lost, unless MemoryDB or ElastiCache synchronous durability (Valkey 9.0 and later) logs each write before confirming it.Can be lost, because replication is asynchronous. WAIT and min-replicas-to-write narrow the window.
Memory, eviction, and slow commandsYours. The provider's default eviction policy may not suit your keys.Yours.
Versions and end of lifeThe provider's calendar. ElastiCache moved Redis OSS 4 and 5 into paid Extended Support in 2026.Your calendar, against Valkey's published maintenance and security dates.
Moving off laterElastiCache restricts PSYNC and REPLICAOF, so bulk data leaves as a backup exported to Amazon S3.Replication to the new target, with writes paused at cutover.

Your team keeps control

  • Set business priorities, application requirements, and release plans
  • Approve production changes, except routine actions you have pre-approved
  • Own your cloud accounts, access policies, and vendor relationships
  • Decide when maintenance can happen and how quickly service must recover
  • Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)

JusDB handles the agreed database work

  • Monitor database health, investigate alerts, and involve the right people
  • Review query performance, replication, capacity, and backup health
  • Carry out approved changes and update the operating instructions they affect
  • Report completed work, open risks, and recommended next steps

Weighing a managed service against running Valkey yourself? We compare both against your workload on a scoping call.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Further reading

Valkey guides and a Redis comparison

Blog guides on licensing, migration, settings, failover, and cache invalidation, plus a Redis comparison.

FAQ

Common Valkey questions

What buyers ask about Redis compatibility, licensing, migration, clusters, and monitoring.

Still have a question?

Ask it on a scoping call. No production access needed.

Book a 30-min scoping call (opens Google Calendar in a new tab)

What is Valkey and how does it differ from Redis?

JusDB works with Valkey, the open-source continuation of Redis OSS that the Linux Foundation formed in March 2024 from Redis 7.2.4. Redis had just moved later releases off the BSD license, while Valkey kept the BSD 3-Clause license and the same protocol. The two have added different features since.

Is Valkey fully compatible with Redis?

Not with every release, so JusDB checks each workload. Valkey loads RDB and AOF files from Redis OSS 7.2 and earlier, and Redis clients connect without code changes. Redis 7.4 and later files are not compatible, and Redis 8 search and JSON need the Valkey Search and Valkey JSON modules.

How do you migrate from Redis to Valkey?

JusDB chooses the path by source version. From Redis OSS 7.2 or earlier, we add Valkey replicas and promote them in a rehearsed cutover with a rollback plan. On ElastiCache, AWS supports an in-place upgrade to Valkey. Data from Redis 7.4 or later needs a different method, because its files are not compatible.

What is the licensing difference between Valkey and Redis?

JusDB summarizes the published terms. Valkey uses the BSD 3-Clause license, as Redis OSS 7.2 and earlier did. Redis 7.4 moved to RSALv2 or SSPLv1, which Redis Ltd. says are not open source, and Redis 8 added AGPLv3. Your legal team should confirm what applies.

Can you help with Valkey cluster setup?

Yes, JusDB designs and builds Valkey Cluster deployments: shard count, replicas across failure zones, and hash tags for keys that must share a slot. We tune cluster-node-timeout to your loss tolerance, and deploy Valkey Sentinel instead where one primary is enough.

What monitoring solutions do you recommend for Valkey?

JusDB uses Prometheus and Grafana with redis_exporter, which supports Valkey 7.x through 9.x, plus INFO, COMMANDLOG, and the latency monitor. We alert on memory headroom, evictions, replica lag, full resyncs, and cluster state, and add CloudWatch metrics on ElastiCache and MemoryDB.

Next step

Talk to a Valkey engineer about your databases

Tell us what is slow, fragile, or due to change. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.

NDA before access, read-only by default, and written scope first