Integrating Redis Cache and CDN on Azure
The course is part of this learning path
This course provides an overview of Redis Cache and how to create a Redis Cache instance in Azure. With Redis Cache deployed in Azure, we’ll then connect an application to the cache.
Next, we’ll walk through the process of storing and retrieving data in Redis Cache. After covering Redis Cache, we’ll walk through an overview of what CDN is and what it’s used for. We’ll then develop some code for leveraging CDN. As we wrap up the course, we’ll cover the process for invalidating data in both Redis Cache and in a CDN.
This course is intended for IT professionals who are interested in earning Azure certification and those who need to incorporate Redis Cache or CDN into their solutions. To get the most from this course, you should have at least a moderate understanding of what caching is and why it’s used.
By the end of this course, you should have a good understanding of what Redis Cache and CDN are and what purposes they serve. You’ll also know how to connect to each from applications and how to purge or invalidate data in both.
- [Instructor] In this demonstration we're going to see how the cache in an Azure CDN can be manipulated using query strings. On your screen you can see I'm in here with my CDN in Azure. On your screen here you can see I'm in my CDN. If I click on my end point that we created in our previous demonstration, I can browse over to caching rules to see what rules are set up for this end point. We can see that we have global caching rules and custom rules. What we're going to do here in this demonstration is change the query string caching behavior. If I select this drop-down you can see there's three options. We have ignore query strings, bypass caching for query strings and cache every unique URL. What we're going to do here is change the default caching behavior to cache every unique URL. And then we'll save it. While this is saving, we'll go out to our web app and we'll refresh here and see that our text is blue. If we go into our cache, we can also see that our text is blue. Now what I'm going to do here is copy my end point URL and open a new tab. I'll paste this URL in, but I'll specify a query string. So we can see here even with a query string of one we still have blue text, which makes sense, we haven't made any changes yet. And I'll just refresh this to make sure it gets committed to cache. And now what I'm going to do is go down into my ftp client and I'm going to edit my web app and I'll change the color to green. So on my production web app this text is now green. So what I'll do next is open up my end point again this time with a query of two. We can see my query two shows green text, my query one shows blue. If I refresh, I still have blue text. So what this demonstrates is how each query string is treated differently based on the fact that I have the query string caching behavior set to cache every unique URL. If we bounce back down to my editor here, and change it to black, I can then open another tab, so another query and now I get black text. So as you can see, you can control what content is cached and how, based on how you configure your caching rules, and how you access the content itself.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.