Transition from Redis to Valkey Q&As

Artur Gołda · June 5

Spryker are upgrading cache engine in our e-commerce architecture from Redis to Valkey, supported by AWS ElastiCache. This change will deliver several advantages, including enhanced performance and scalability, as well as ongoing security patches, all with zero disruption to customer operations.

Those with questions can use this thread to ask questions directly to Spryker's tech team. All relevant parties should have been contacted regarding this transition, but if you think this may be relevant to you, more information can be found below. Please do not hesitate to ask questions in this thread.

What Will Take Place

Phased rollout: Starting 5 June (Week 23) through August
Zero downtime: Core migration fully managed by Spryker
Notifications: Customers/partners will be notified 14 days in advance of any environment-specific changes

What Do Partners or Customers Need to Do?

Minimal action required
Update DockerSDK in local dev environments for compatibility
Compatibility checks on transitioned environments
No cloud environment changes needed
Partners: Please notify customers and include QA in sprint planning

Key Benefits

Up to 5x faster write throughput
Better scalability, failover, and memory efficiency
Ongoing security patches and simplified licensing
Long-term support backed by AWS, Google Cloud, Oracle, and more

This upgrade ensures continued reliability and future-readiness for your e-commerce operations. Please ask any questions below.

LukasB · June 16

Hello,

one related question. I've tried out Valkey in one of my projects and it seems to work fine on my local dev machine. The only thing thats not working is the redis commander. It refuses to connect to Valkey on my end.

Is that somehow expected? Did you experience something similar? Is there any replacement for it?

fsmeier · June 16

Heyhey @LukasB ,

a fix is available in the latest docker-sdk master and within the tag https://github.com/spryker/docker-sdk/releases/tag/1.67.0

All the best,

Florian

LukasB · June 17

Thanks @fsmeier

Works well now 😊

andreas.fluer · June 18

Hi everyone,

We’ve updated our deploy file for local development to use Valkey instead of Redis, following the instructions provided in the documentation. However, as recommended, we have not yet made any changes to the deploy files for our stage and production environments.

We’re currently trying to understand how the transition to Valkey should work in these non-local environments. Specifically:

How does the switch to Valkey work on stage and prod if the deploy files remain unchanged?
At what point should we consider updating these deploy files to reflect the new configuration?
Should we remove all Redis references from the stage/prod deploy files entirely, or will that be handled automatically by Spryker?

Any detailed guidance or clarification on how to safely and correctly manage this transition would be greatly appreciated.

Best, Andreas

Artur Gołda · June 18

@andreas.fluer thx for your message!

Answering your questions:

How does the switch to Valkey work on stage and prod if the deploy files remain unchanged?

For cloud workloads, this is infra configuration managed by Spryker, not deploy file, that defines cache engine. This is why we can do this transition smoothly on our end.

At what point should we consider updating these deploy files to reflect the new configuration?

In general - Valkey, within the context of Spryker app, is 100% compatible with Redis 6.2. So - feel free to change it whenever it suits you.

Should we remove all Redis references from the stage/prod deploy files entirely, or will that be handled automatically by Spryker?

You don't need to do anything to deploy file (just adjust file to your local development needs). We will take care of everything on the cloud.

Transition from Redis to Valkey Q&As

Comments

Categories