As an alternative of 1 occasion per VM, you’re now in a position to stack a number of cases behind a Redis proxy. There’s one other massive change: Though you continue to use two nodes, each nodes run a mixture of major and reproduction 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 reproduction nodes robotically 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 possibility is similar as utilized by the group version, with direct connections to particular person shards. This works properly, with close-to-linear scaling, nevertheless it does require particular assist in any consumer libraries you’re utilizing in your code. The choice, Enterprise, works by means 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 software for preserving frequently accessed information cached in reminiscence, permitting fast learn/write entry. It’s getting used anyplace you want a quick key/worth retailer with assist for contemporary options corresponding to 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 current output, utilizing it as semantic reminiscence in frameworks like Semantic Kernel.
