The concept of a geo-replicated partnership between a primary and secondary node is very similar to that of something you may have seen with Azure SQL DB, where the primary handles all R/W and then the changes are pushed to secondary ( async). This is no different with Redis.
Let’s assume that you started off with the lower editions and capacity with Redis and your developers tell you to scale the Redis cluster. Well first to use a cluster you need premium. Below under the cluster size option in the Azure portal you will see the message:
My learnings on Redis thus far which you may find useful:
Now that we have created our Redis Cache lets connect to it. You can use the most common tool redis cli.exe https://redis.io/download or as I am going to do, use the Azure Portal to use the console directly, this isn’t probably the best way but it’s the easiest for this blog. 2 key points here:
Let’s go through a Redis build process. It will be fun.
Redis Cache is a well know caching technology and you can run it in Azure as a fully managed service. A common requirement (the most basic one) is doing a workflow like:
All About Data 