Utilizing RESP to hyperlink Valkey to code
.NET Aspire’s present Redis shopper will work with Valkey; all it’s essential do is be certain that you’re utilizing the right connectionName. Microsoft supplies Aspire implementation particulars for 3 totally different Valkey situations: normal cache, distributed cache, and output cache. The documentation isn’t fairly full, because it typically refers to Redis somewhat than Valkey, however Aspire treats the 2 interchangeably so it’s not too obscure what to do and when.
One other benefit to utilizing Valkey with Aspire: You may reap the benefits of Aspire’s observability instruments, well being checks, logging, and its built-in developer dashboard to observe operations—together with your cache. Having instruments that handle utility well being is necessary, particularly when constructing the distributed, cloud-native purposes that depend on providers like Valkey.
As Valkey continues to diverge from Redis, it’s price keeping track of each initiatives, as every will handle totally different use instances and help totally different utility architectures. For now, nevertheless, due to RESP, they can be utilized comparatively interchangeably, permitting you to decide on one or the opposite and swap to whichever works greatest for you and your venture. With primary help in each AKS and .NET Aspire, and a significant new launch of Valkey across the nook, it’s an appropriate time to present it a strive.