Using Valkey on Azure and in .NET Aspire

".NET Aspire's existing Redis client will work with Valkey; all you need to do is ensure that you're using the correct connectionName. Microsoft provides Aspire implementation details for three different Valkey scenarios: standard cache, distributed cache, and output cache. The documentation isn't quite complete, as it often refers to Redis rather than Valkey, but Aspire treats the two interchangeably so it's not too difficult to understand what to do and when."

"Another advantage to using Valkey with Aspire: You can take advantage of Aspire's observability tools, health checks, logging, and its built-in developer dashboard to monitor operations-including your cache. Having tools that manage application health is important, especially when building the distributed, cloud-native applications that rely on services like Valkey. As Valkey continues to diverge from Redis, it's worth keeping an eye on both projects, as each will address different use cases and support different application architectures. For now, however, thanks to RESP, they can be"

Aspire's existing Redis client works with Valkey when using the correct connectionName. Microsoft provides Aspire implementation details for three Valkey scenarios: standard cache, distributed cache, and output cache. Aspire's documentation often refers to Redis rather than Valkey, yet Aspire treats them interchangeably, making configuration straightforward. Valkey integration enables use of Aspire's observability tools, health checks, logging, and built-in developer dashboard to monitor operations including cache. Application health tooling supports distributed, cloud-native applications that rely on services like Valkey. RESP protocol compatibility currently allows Valkey and Redis to be used interchangeably. Basic support exists in AKS and .NET Aspire, and a major Valkey release is imminent.

Read at InfoWorld