A post close to my heart, Azure SQL Managed Instance, I have blogged about this many times but I feel I should be sharing more details about this. One important topic – Maintenance windows.
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.
I mentioned before that you could use the idea of data persistency to rebuild your data from total failure. There are two types. RDB and AOF.
RDB – persists a snapshot of your cache in a binary format. The snapshot is saved in an Azure Storage account. AOF – saves every write operation to a log. The log is saved at least once per second into an Azure Storage account.
This is quite an in-depth topic area and I suggest further reading to determine which one suits you: https://redis.io/topics/persistence#aof-disadvantages
To set this up you will see data persistence section within your Redis Cache
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:
If you navigate to the overview section of your MySQL server you will see a notification area, here you will find security section. It’s basically an area to provide some hints / tips if things have not been configured such as if you have not enabled query store it may well suggest it. For this blog it is suggesting I consider a feature called Microsoft Defender.
The query store, sounds familiar? The idea of the black box sitting within the database server watching what is going on within the environment. This is available within MySQL, maybe not as feature rich as SQL Server but still useful.
You will find this option under the Query performance insight section of your MySQL server.