As a substitute 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 assets than a duplicate, so this method helps you to get the absolute best efficiency out of your VMs. On the similar time, this mixture of major and reproduction nodes mechanically clusters information to hurry up entry and allow assist 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 group version, with direct connections to particular person shards. This works nicely, 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 device for holding frequently 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 comparable 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 era (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.
