Redis, Valkey & Caching Engineering
Redis changed its licence in 2024, Valkey forked under the Linux Foundation, and Microsoft is retiring Azure Cache for Redis. We help you choose between Redis and Valkey, move caches without dropped sessions and design caching that holds up under load.

Dates that drive this work
- days Azure Azure Cache for Redis Enterprise and Enterprise Flash tiers retire.ics
- days Azure Azure Cache for Redis Basic, Standard and Premium tiers retire.ics
Sources: Microsoft Learn: Azure Cache for Redis retirement FAQ
Sound familiar?
- Legal flagged the Redis licence change and wants to know whether Valkey removes the question.
- You run Azure Cache for Redis Enterprise, which retires on March 31, 2027, or Basic, Standard or Premium, which retire on September 30, 2028.
- ElastiCache for Valkey costs less than Redis OSS and you want the saving without a risky cut-over.
- Cache misses, hot keys or evictions are causing latency spikes nobody can explain.
What you receive
- Inventory and licence position
- Target recommendation with cost comparison
- Migration runbook with rollback
- Terraform for the new clusters
- Load-test and latency report
What we deliver
Scope is confirmed in writing in the assessment, with anything out of scope listed too.
- 01
Licence and target choice
Redis 8 (RSALv2, SSPLv1 or AGPLv3) versus Valkey (BSD) versus a managed service, explained plainly for engineering and legal.
- 02
Compatibility check
Client libraries, commands, modules (search, JSON, time series) and data file formats checked before anything moves.
- 03
Managed service moves
ElastiCache, MemoryDB, Memorystore for Valkey, Azure Managed Redis or Redis Cloud, sized and deployed with Terraform.
- 04
Cut-over
Replication, dual writes or the cloud provider's migration tooling, chosen to avoid lost sessions.
- 05
Caching design
TTLs, eviction policy, key design, cluster mode and connection pooling tuned for your traffic.
- 06
Vector and AI use
Where it fits, Redis or Valkey search used as a low-latency vector or semantic cache.
Fixed scope and a fixed fee, agreed in writing.
Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.
Step 01
Caching review & migration plan
Fixed fee, scoped after the free review
Inventory, licence position, target choice (Valkey, Redis, managed service), client compatibility, risks and a fixed quote. Credited toward the migration.
Step 02
Migration
Fixed fee, scoped after the free review
Scoped per cluster or environment from the plan, agreed in writing before work starts.
Samples and an example engagement
Templates with fictional systems and an illustrative scope, so you can judge the depth before the first call.
Redis to Valkey on ElastiCache
An engineering team pays for self-managed Redis and ElastiCache for Redis and wants to know whether Valkey is a safe, cheaper drop-in after the Redis licence change.Sample deliverableSample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.Sample deliverableSample cut-over runbook: PostgreSQL major upgrade with blue/green
A step-by-step runbook excerpt with timings, owners, checks and the rollback path.From first call to delivery
You can stop after any step and keep everything we have written.
- 01
Free
Free 30-minute review
We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.
- 02
1 week · credited
Caching review
Target choice, compatibility findings and a fixed quote.
- 03
Typically 1–4 weeks
Migration
Rehearsed cut-over per environment.
Technologies
Names are trademarks of their owners. Listing does not imply partnership.
Questions about this service
Straight answers on scope, fees and how we work. Anything else, ask us.
Is Redis still open source?
Redis 7.4 moved to RSALv2 or SSPLv1. Redis 8 added AGPLv3 as a third option, which is OSI-approved but carries network copyleft obligations. Valkey, forked from Redis 7.2.4, remains BSD-licensed. Have counsel confirm how this applies to you.
Can Valkey read our Redis data?
Valkey reads the data files of Redis OSS 7.2 and earlier. Data from Redis 7.4 and later needs a logical migration rather than a file copy.
What happens if we ignore the Azure Cache for Redis retirement?
Microsoft says remaining Enterprise caches are migrated or disabled from April 1, 2027, and Basic, Standard and Premium caches are disabled from October 1, 2028.
Is the review fee credited?
Yes, in full, toward the migration if you go ahead.
Start with a free 30-minute review.
Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.
