Free audit

View Audit Scope
JusDBLinux Foundation BSD-3 · Valkey 7.2 & 8.0 · Sentinel · Cluster · Redis Transition

Valkey consulting for BSD-3 architecture, memory sizing, and 8.0 scale.

JusDB provides Valkey consulting for engineering teams transitioning off Redis 7.2+ licensing or designing high-throughput in-memory architectures. We audit SDKs and Lua/module compatibility, size maxmemory and copy-on-write fork headroom, decide between Sentinel HA and 16,384-slot Cluster sharding, and tune Valkey 8.0 multi-threaded I/O before changes touch production.
The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or start with a free read-only Valkey / Redis fleet audit.
  • NDA before access
  • Read-only by default
  • Written scope before work starts

valkey_architecture_audit

Valkey 8.0 / 7.2

Zero SSPLv1 / RSALv2 license restrictions

Deliverables: BSD-3 transition roadmap, valkey.conf diff, memory math & topology blueprint.

Open-Source Governance
Linux Foundation BSD-3
Exit RSALv2 / SSPLv1 restrictions with full RESP2/RESP3 wire compatibility
Valkey 8.0 Engine
Multi-Thread Async I/O
io-threads, dual-channel replication, and reduced per-key dictionary overhead
Memory Safety
CoW Fork Headroom
maxmemory, client output buffers, and activedefrag sized against OOMKills
P1 target (24x7 on-call)
15 minutes
Initial response under a 24x7 support agreement (2 to 4 hours business hours)

Selected clients

  • Innoviti
  • Blitz
  • Freecharge
  • Nango
  • Recochain
  • Screen Facts
  • Nexora
  • WeCredit

Architectural challenges we solve

Six reasons teams bring in our Valkey architects.

From navigating the Redis 7.4+ license change to preventing copy-on-write fork OOMs and choosing between Sentinel and Cluster mode.

REDIS_7_4_LICENSE_EXPOSURE

Legal and procurement teams block Redis upgrades past 7.2.4 due to RSALv2 / SSPLv1 dual licensing

What is usually happening
Redis Inc. changed the license of Redis 7.4+ away from BSD-3, creating compliance friction for SaaS platforms, embedded products, and enterprise fleets.
Where we start
Audit every Redis instance version, client SDK, and module across your fleet, and map a clean transition roadmap to Linux Foundation BSD-3 Valkey 7.2 or 8.0.
PREMATURE_CLUSTER_SHARDING

Application suffers CrossSlot errors and operational complexity on a 20 GB dataset

What is usually happening
Teams deployed 16,384-slot Cluster mode when a simpler 1-primary + 2-replica Sentinel topology would easily fit in RAM and support multi-key transactions.
Where we start
Benchmark working-set memory and single-core command throughput to choose deterministically between Sentinel HA and sharded Valkey Cluster.
COW_FORK_OOM_CRASH

Linux OOMKiller terminates valkey-server during peak-hour BGSAVE or BGREWRITEAOF

What is usually happening
maxmemory was set to 85-90% of host RAM without reserving copy-on-write (CoW) page-table headroom for child fork() processes under heavy write mutation.
Where we start
Right-size maxmemory at 60-70% of physical RAM on write-heavy nodes, enable vm.overcommit_memory=1, and schedule RDB/AOF rewrites safely.
REDIS_STACK_MODULE_LOCKIN

Migration to Valkey stalls because legacy services use RediSearch, RedisJSON, or RedisTimeSeries

What is usually happening
Source-available Redis Stack modules are not licensed under BSD-3 and require community Valkey modules (valkey-json, valkey-search) or native data-structure refactoring.
Where we start
Inventory module commands via INFO modules and MONITOR samples, and design drop-in Valkey 8.0 module replacements or native Hash/ZSET/Stream patterns.
CLOUD_CACHE_COST_SPRAWL

Managed cloud cache bills spiral because oversized instances sit at 18% memory utilization

What is usually happening
Clusters were provisioned for peak connection counts or un-TTL'd keys without key-prefix memory profiling or Valkey 8.0 multi-threaded I/O.
Where we start
Run valkey-cli --bigkeys and --memkeys sampling, enforce TTL hygiene, and consolidate shards using Valkey 8.0 dual-channel replication and async I/O threads.
CLIENT_RESP3_VERSION_CHECK

Legacy client library refuses to connect or logs warnings against Valkey 8.0 server banners

What is usually happening
Certain older SDKs parse INFO server redis_version strings literally or lack tuned connection-pool timeouts for cloud network hops.
Where we start
Audit Lettuce, Jedis, go-redis, ioredis, and valkey-glide client configurations, verify server-version reporting settings, and tune pool sizing.

Consulting scope

Six engineering workstreams inside a Valkey consulting engagement.

Scoped around your fleet size, cloud platform, and durability requirements. Every workstream delivers a written engineering artifact.

01

Redis-to-Valkey BSD-3 Strategy & Fleet Audit

A complete inventory and architectural roadmap for transitioning off Redis 6.x/7.2 onto Linux Foundation Valkey 7.2 or 8.0 without licensing exposure.

  • Audit of Redis Stack modules, Lua scripts, Functions, and ACL rules across every cluster
  • Side-by-side comparison of ElastiCache Valkey, GCP Memorystore for Valkey, and self-hosted VMs/K8s
INFO modules · ACL LIST · /compare/redis-vs-valkey
Compare Redis vs Valkey
02

Topology Selection (Sentinel vs Cluster Mode)

Data-driven decision modeling so you only take on 16,384-slot Cluster sharding when your working set or write rate genuinely requires it.

  • Single-primary + Sentinel HA sizing for datasets under 64-128 GB requiring multi-key ops
  • Valkey Cluster shard count and hash-tag {tenant} design for multi-hundred-GB scale
Sentinel · Cluster 16,384 Slots · Hash Tags
Valkey Cluster engineering
03

Valkey 8.0 Architecture & Memory Sizing

Right-sizing physical RAM, maxmemory, copy-on-write fork headroom, and Valkey 8.0 multi-threaded I/O for predictable latency.

  • Exact maxmemory, replica-output-buffer, and CoW fork safety math per instance family
  • Valkey 8.0 io-threads, dual-channel replication, and dictionary overhead optimization
INFO memory · io-threads · vm.overcommit_memory
Valkey performance tuning
04

Key-Structure, Eviction & Persistence Design

Aligning data structures (Hashes, ZSETs, Streams, Bitmaps), TTL policies, and RDB/AOF durability with your application's RPO budget.

  • Selecting maxmemory-policy (allkeys-lru, allkeys-lfu, volatile-ttl, noeviction)
  • Balancing RDB snapshot intervals and AOF appendfsync everysec against disk IOPS
maxmemory-policy · AOF / RDB · listpack encodings
05

Client SDK, Valkey GLIDE & Connection Pooling

Reviewing application client libraries so connection storms, blocking commands, and failover reconnects do not stall request threads.

  • Evaluation of Valkey GLIDE, ioredis, go-redis, Lettuce, and redis-py connection pools
  • Pipelining, Lua script atomicity, and removal of O(N) KEYS/SMEMBERS anti-patterns
Valkey GLIDE · Lettuce / go-redis · SLOWLOG
06

Migration Blueprint & Cutover Readiness

Delivering a step-by-step execution specification for moving live production caches and session stores to Valkey without cold-cache outages.

  • REPLICAOF live replication sync or cloud in-place engine conversion runbooks
  • Pre-cutover checklist, parity verification scripts, and instant DNS/VIP rollback gates
REPLICAOF · aws elasticache · Cutover Runbook
Redis to Valkey migration

Shared responsibility & response targets

Managed cache control planes vs Valkey architecture engineering.

AWS ElastiCache and GCP Memorystore provision virtual machines, but topology selection, maxmemory fork safety, eviction policy, and key design remain your team's responsibility.

Cloud instances & managed cache control plane
ElastiCache / Memorystore provisions VMs and basic failover.
Your infra team provisions VMs or K8s nodes; JusDB specifies RAM-to-vCPU ratios and kernel sysctls.
BSD-3 licensing & Redis module transition
Cloud vendor offers engine toggle; does not audit app modules.
JusDB audits Lua scripts, Redis Stack modules, and SDKs for clean Valkey 8.0 adoption.
Topology choice (Sentinel vs Cluster)
Customer chooses cluster mode at creation time.
JusDB models dataset growth and multi-key access patterns to select the right topology.
maxmemory, CoW fork headroom & eviction
Defaults leave write-heavy nodes vulnerable to swap/OOM.
JusDB calculates exact maxmemory, output buffers, activedefrag, and eviction policies.
Key design, TTL hygiene & client pooling
Never reviewed by cloud infrastructure providers.
JusDB profiles bigkeys/hotkeys, compact encodings, and SDK connection pools.
Initial-response targets (when retained for support)

Severity matrix for retained Valkey fleets

Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees. 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.

SeverityCondition24x7 TargetBusiness Hours
P1 · CriticalProduction database down, primary unreachable, data corruption risk, or active failover event.15 minutes2 to 4 hours
P2 · HighSevere latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.30 minutes2 to 4 hours
P3 · MediumNon-critical slow query regression, staging issue, backup warning, or replication check alert.60 minutes2 to 4 hours
P4 · LowConfiguration question, index advisory, planned schema review, or general operational request.90 minutes2 to 4 hours

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

Your team retains

Access & cloud governance

  • 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 (see Terms, section 8)
JusDB owns

Engineering deliverables

  • 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

Interactive architecture state simulator

Compare an unmodeled cache against an engineered Valkey 8.0 deployment.

Select a state below to inspect how copy-on-write fork headroom, Valkey 8.0 dual-channel replication, and topology sizing prevent OOM crashes.

valkey_architecture_simulator

Application and routing

Client Pool -> Valkey 8.0 Primary (io-threads=4) -> Dual-Channel Async Replica Sync

Active
  • valkey-primary-01 (64GB Host)

    maxmemory=42GB (65% RAM)

    frag_ratio=1.06 · CoW fork headroom=22GB · p99=0.3ms

  • valkey-replica-01 & 02

    Valkey 8.0 Dual-Channel Sync

    repl_offset_lag=0B · RDB offloaded to replica

  • Sentinel Quorum (3 AZs)

    Split-Brain Guarded

    quorum=2/3 · min-replicas-to-write=1 verified

maxmemory leaves 35% physical RAM for copy-on-write fork pages and client buffers, Valkey 8.0 dual-channel replication prevents full-resync stalls, and Sentinel quorum spans 3 AZs.

Sample consulting deliverable

Read-only memory & module audit and valkey.conf specification.

Every consulting finding includes non-blocking valkey-cli diagnostic commands and the target configuration diff.

Finding #02 · Memory & Fork Audit

Eliminating BGSAVE copy-on-write OOMKills and upgrading Redis 7.2 to Valkey 8.0

A 64 GB primary instance had maxmemory set to 56 GB (87.5% of host RAM) with activedefrag no. During peak write hours, BGSAVE child processes generated 11 GB of copy-on-write pages, triggering the Linux OOMKiller.

Architectural fix: Lowered maxmemory to 42 GB (65% of RAM), enabled lazyfree-lazy-eviction yes and activedefrag yes, and upgraded to Valkey 8.0 with io-threads 4 and dual-channel replication.
Persistence offload: Disabled RDB snapshots on the primary (save "") and scheduled RDB backups exclusively on the dedicated backup replica.
Diagnostic collection: Read-only INFO / MEMORY STATS · Zero blocking KEYS scans

01 · Read-only memory fragmentation, CoW fork & module compatibility audit

# 1. Inspect used_memory_rss, fragmentation ratio, and last fork CoW size (mem_not_counted_for_evict)
valkey-cli INFO memory | grep -E "used_memory_human|used_memory_rss_human|mem_fragmentation_ratio|maxmemory_human|current_cow_size"

# 2. Check persistence fork duration (latest_fork_usec) and loaded modules / Lua functions
valkey-cli INFO persistence | grep -E "rdb_last_bgsave_status|latest_fork_usec|aof_rewrite"
valkey-cli INFO modules
valkey-cli FUNCTION LIST

# 3. Non-blocking cursor sample of key sizes and memory footprints (uses SCAN, never KEYS *)
valkey-cli --memkeys -i 0.05

02 · Target Valkey 8.0 production configuration (valkey.conf)

# Valkey 8.0 Multi-threaded network I/O & CoW-safe memory boundaries (on 64GB host)
io-threads 4
io-threads-do-reads yes
maxmemory 42gb
maxmemory-policy allkeys-lfu

# Non-blocking asynchronous memory reclamation & jemalloc defragmentation
lazyfree-lazy-eviction yes
lazyfree-lazy-expire yes
lazyfree-lazy-server-del yes
replica-lazy-flush yes
activedefrag yes
active-defrag-ignore-bytes 500mb
active-defrag-threshold-lower 10

# Offload RDB snapshots from primary; use diskless dual-channel replication
save ""
repl-diskless-sync yes
min-replicas-to-write 1
min-replicas-max-lag 10
Evaluation Vector
JusDB DBRE
In-House DBALegacy AgencyDeveloper Generalist
Sentinel vs 16,384-Slot Cluster Topology SizingComprehensive dataset capacity and write QPS modeling; determines precise crossover threshold between Sentinel single-primary failover and 16,384-slot distributed cluster topology with custom shard balancing.Deploys Cluster mode prematurely for sub-10GB datasets adding unnecessary gossip protocol overhead, or forces Sentinel beyond single-core write saturation limits.Treats Valkey strictly as a legacy standalone Redis cache; lacks architectural modeling for dynamic slot sharding, failover timeouts, or replica migration.Relies on cloud vendor auto-clustering defaults; misses slot distribution skew and triggers cluster-wide OOM outages during traffic spikes.
Redis-to-Valkey Migration & Licensing GovernanceLow-downtime cutover engineering via dual-replication pipelines, client SDK protocol compatibility audits (RESP2/RESP3), and BSD-3 license indemnity against SSPL/RSAL lock-in.Postpones migration due to legal uncertainty around Redis 7.4+ dual licensing; attempts manual dumps with hours of maintenance downtime.Recommends staying on deprecated Redis OSS releases without understanding upstream CVE patching gaps or Linux Foundation Valkey governance.Executes abrupt DNS flips without validating client driver clustering support or warming cold in-memory caches, causing massive database stampedes.
Multi-Threaded I/O (io-threads) & Concurrency ArchitectureCalibrates io-threads and io-threads-do-reads based on physical NUMA cores, pinning event loops and tuning socket buffers to exceed 1.2M ops/sec with sub-millisecond p99 latency.Leaves Valkey in default single-threaded I/O mode on 32-core cloud instances, leaving 90% of provisioned hardware compute unutilized.Blindly sets io-threads to total vCPU count, causing severe thread context switching contention and elevating p99 tail latency.Unaware of Valkey multi-threaded architecture; blames network latency for CPU-bound socket buffer saturation.
Hash-Tag Routing & Cross-Slot Transaction StrategyDesigns schema hash-tag ({tenant_id}) partitioning models and Lua script routing guardrails to guarantee multi-key atomicity while preventing single-slot hot-spotting.Attempts cross-slot multi-key transactions without hash tags, encountering fatal CROSSSLOT Keys in request don't hash to the same slot runtime errors.Disables multi-key operations entirely in application layers instead of architecting proper hash-tag keyspace distribution.Aggressively groups all keys under a single global hash tag, defeating cluster sharding and funneling entire database load into one primary node.
Persistence Engine Selection (RDB vs AOF vs Dual)Tailored persistence profiling balancing RPO/RTO against latency; implements AOF everysec with background rewrite budgeting and scheduled off-peak RDB snapshots.Enables aggressive AOF appendfsync always on high-write systems, crushing NVMe disk IOPS and stalling the main command execution thread.Relies exclusively on standard hourly RDB snapshots; risks up to 60 minutes of unrecoverable committed transactions upon node power failure.Disables persistence entirely for ephemeral caching without evaluating replica resync storms or cold-cache stampedes on upstream relational stores.
Enterprise Zero-Trust Security, TLS & RBAC HardeningEnd-to-end mutual TLS (mTLS) encryption, granular Redis/Valkey ACL v2 user definitions, command masking (FLUSHALL, CONFIG), and automated certificate rotation.Relies on simple requirepass shared passwords without user-level privilege separation or internal replica transport encryption.Leaves administrative commands unmasked and defaults to plaintext port 6379 across VPC peering connections.Exposes Valkey instances to public subnets with disabled protected-mode for remote troubleshooting, inviting ransomware attacks.

Engagement models

Three ways to engage our Valkey architects.

Start with a fixed-scope architecture and BSD-3 transition audit, or pair it with hands-on migration and Remote DBA operations. A monthly retainer for a set number of engineering hours, or a monthly fee per database instance, HA cluster, or region; projects are scoped and quoted separately.

Fixed-Scope Advisory

Architecture & BSD-3 Fleet Audit

Written evaluation of Redis-to-Valkey compatibility, Sentinel vs Cluster sizing, maxmemory fork math, and Valkey 8.0 parameter tuning.

Project Execution

Redis-to-Valkey Migration

Hands-on REPLICAOF live replication cutovers or ElastiCache/Memorystore engine conversions with zero cold caches and instant rollback gates.

Retained Operations

Remote DBA & Incident Support

Ongoing fleet monitoring, rolling upgrades, or reactive P1 incident response under a 24x7 support agreement.

Procurement and security

Ready for legal and security review.

Mutual NDA before any access, least-privilege credentials in your vault, and security controls aligned with ISO 27001 and SOC 2 Type II.
  • Mutual NDA before any access
  • Named individual accounts only
  • Read-only access by default
  • ISO 27001 & SOC 2 Type II: aligned, certification in progress
  • Mutual NDA before any access

    We sign a mutual NDA before viewing schemas, logs, slow-query captures, or cloud topology.

  • Least-privilege, named credentials

    Engineers connect through your bastion, VPN, or SSM using named accounts with read-only permissions by default.

  • Change control & approval gates

    Production DDL, parameter changes, and failovers follow your change-management workflow with rollback steps prepared first.

  • Named leadership & direct escalation

    Engagements are led by named senior database reliability engineers in India with direct Slack, Teams, and PagerDuty channels.

Valkey consulting FAQ

BSD-3 licensing, Valkey 8.0, and topology questions.

Direct answers on Redis-to-Valkey compatibility, Sentinel vs Cluster mode, and how JusDB scopes consulting work.

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)

Why are engineering teams moving from Redis to Valkey?

In March 2024, Redis Inc. changed the license of Redis (starting with Redis 7.2.4 / 7.4) from the permissive 3-clause BSD license to dual RSALv2 and SSPLv1 licenses. Valkey was forked from Redis 7.2.4 under the Linux Foundation with the backing of AWS, Google Cloud, Oracle, Ericsson, and Snap to keep the in-memory datastore permanently open-source under the BSD-3 license. Valkey 8.0 adds major performance improvements including enhanced multi-threaded I/O and dual-channel replication.

What deliverables do we receive from a Valkey consulting engagement?

You receive a written architectural dossier: a fleet-wide Redis-to-Valkey compatibility audit, Sentinel vs Cluster topology sizing math, annotated valkey.conf (or ElastiCache/Memorystore parameter group) diffs, maxmemory and copy-on-write fork calculations, key-structure and TTL recommendations, and a step-by-step migration and rollback runbook.

How do we decide between Valkey Sentinel and Valkey Cluster mode?

If your working set fits comfortably inside a single node's maxmemory budget (typically under 64-100 GB) and your write throughput is below single-core saturation (~100k-150k ops/sec, or higher with Valkey 8.0 io-threads), a single primary with replicas and Sentinel is simpler and supports arbitrary multi-key transactions and Lua scripts. Once your dataset or write throughput exceeds a single node, we architect a sharded 16,384-slot Valkey Cluster (/databases/valkey/cluster).

What if our application uses RedisJSON, RediSearch, or custom Lua scripts?

Standard Lua scripts (EVAL / EVALSHA) and Redis 7.2 Functions work identically in Valkey. If your workload uses source-available Redis Stack modules like RedisJSON or RediSearch, we audit how those commands are used and either map them to Linux Foundation Valkey modules (such as valkey-json, valkey-bloom, or valkey-search) or refactor the access pattern into native Valkey Hashes, Sorted Sets, and Streams.

How do you prevent OOM crashes during Valkey RDB snapshots and AOF rewrites?

When Valkey executes BGSAVE or BGREWRITEAOF, the Linux kernel forks the process. Under heavy write traffic, copy-on-write (CoW) duplicates modified memory pages. We size maxmemory at 60-70% of physical RAM on write-heavy primaries, enable Valkey 8.0 dual-channel replication, set vm.overcommit_memory=1, disable transparent hugepages (THP), and offload RDB snapshots to replicas.

How does Valkey consulting differ from Remote DBA, Support, and Migration execution?

Valkey consulting is a fixed-scope advisory and architecture engagement that gives you the written design and parameter plan. Hands-on cutover execution lives on our Migration page (/databases/valkey/migration), continuous day-2 operations live under Remote DBA (/databases/valkey/remote-dba), and reactive emergency firefighting lives under Support (/databases/valkey/support). A monthly retainer for a set number of engineering hours, or a monthly fee per database instance, HA cluster, or region; projects are scoped and quoted separately.

What response targets apply if we retain JusDB for ongoing Valkey coverage?

Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees. 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.

Valkey engineering ecosystem

Related Valkey services across the lifecycle.

Each Valkey service page covers a dedicated operational stage so you can pair architectural consulting with targeted execution.

Comparison

Redis vs Valkey Deep Dive

Detailed architectural, licensing (BSD-3 vs RSALv2/SSPLv1), and Valkey 8.0 feature comparison.

Explore service
Migration

Redis to Valkey Migration

Live REPLICAOF replication cutovers and ElastiCache/Memorystore conversions with zero cold caches.

Explore service
Sharding

Valkey Cluster Services

16,384 hash-slot sharding, hash-tag design, MOVED/ASK client routing, and online slot rebalancing.

Explore service
Resilience

Valkey High Availability

Sentinel quorum engineering, cross-AZ replica promotion, and split-brain prevention.

Explore service
Optimization

Valkey Performance Tuning

Valkey 8.0 multi-threaded I/O, jemalloc activedefrag, eviction tuning, and bigkey remediation.

Explore service
Operations

Valkey Remote DBA & Support

Continuous fleet operations or 15-minute P1 incident response under a 24x7 support agreement.

Explore service

Related Valkey Services

Explore more ways our Valkey experts can help with your database infrastructure.

Start with a written Valkey architecture scope

Design your Valkey 8.0 topology and BSD-3 roadmap with senior DBREs.

Speak directly with a Valkey architect. We start with read-only INFO telemetry and deliver a written engineering plan with exact configuration diffs.