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 large change: Though you continue to use two nodes, each nodes run a mixture of main and duplicate processes. A main occasion makes use of extra sources than a reproduction, so this method helps you to get the absolute best efficiency out of your VMs. On the identical time, this mixture of main and duplicate nodes routinely clusters information to hurry up entry and allow assist for geo-replication throughout areas.
Azure Managed Redis has two completely different clustering insurance policies, OSS and Enterprise. The OSS choice is identical as utilized by the group version, with direct connections to particular person shards. This works effectively, with close-to-linear scaling, but it surely does require particular assist in any shopper libraries you’re utilizing in your code. The choice, Enterprise, works by way of a single proxy node, simplifying connection necessities for shoppers on the expense of efficiency.
Why would you utilize Redis in an software? In lots of instances it’s a device for maintaining repeatedly accessed information cached in reminiscence, permitting fast learn/write entry. It’s getting used anywhere you want a quick key/worth retailer with assist for contemporary options resembling vector indexing. Utilizing Redis as an in-memory vector index helps preserve latency to a minimal in AI functions primarily based on retrieval-augmented technology (RAG). Cloud-native functions can use Redis as a session retailer to handle state throughout container functions, so AI functions can use Redis as a cache for current output, utilizing it as semantic reminiscence in frameworks like Semantic Kernel.
