Utilizing RESP to hyperlink Valkey to code
.NET Aspire’s present Redis shopper will work with Valkey; all it’s essential do is make sure that you’re utilizing the right connectionName. Microsoft gives Aspire implementation particulars for 3 completely different Valkey eventualities: normal cache, distributed cache, and output cache. The documentation isn’t fairly full, because it typically refers to Redis reasonably 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 benefit from 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 essential, particularly when constructing the distributed, cloud-native purposes that depend on providers like Valkey.
As Valkey continues to diverge from Redis, it’s value maintaining a tally of each initiatives, as every will tackle completely different use circumstances and help completely different utility architectures. For now, nonetheless, because of 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 challenge. With primary help in each AKS and .NET Aspire, and a significant new launch of Valkey across the nook, it’s an acceptable time to provide it a strive.