As an alternative of 1 occasion per VM, you’re now capable of stack a number of situations behind a Redis proxy. There’s one other huge change: Though you continue to use two nodes, each nodes run a mixture of major and duplicate processes. A major occasion makes use of extra sources than a reproduction, so this method enables you to get the very best efficiency out of your VMs. On the identical time, this mixture of major and duplicate nodes robotically clusters information to hurry up entry and allow help for geo-replication throughout areas.
Azure Managed Redis has two totally different clustering insurance policies, OSS and Enterprise. The OSS possibility is identical as utilized by the neighborhood version, with direct connections to particular person shards. This works nicely, with close-to-linear scaling, but it surely does require particular help in any consumer libraries you’re utilizing in your code. The choice, Enterprise, works by a single proxy node, simplifying connection necessities for shoppers on the expense of efficiency.
Why would you employ Redis in an software? In lots of circumstances it’s a instrument for protecting usually accessed information cached in reminiscence, permitting fast learn/write entry. It’s getting used anywhere you want a quick key/worth retailer with help for contemporary options resembling vector indexing. Utilizing Redis as an in-memory vector index helps maintain latency to a minimal in AI purposes primarily based on retrieval-augmented technology (RAG). Cloud-native purposes can use Redis as a session retailer to handle state throughout container purposes, so AI purposes can use Redis as a cache for latest output, utilizing it as semantic reminiscence in frameworks like Semantic Kernel.
