Summary

Completed

In the module, we saw how Azure Cache for Redis can help improve our application's performance in many ways. We first saw how transactions can be used to ensure that multiple operations are invoked together, without being interrupted. We then saw how to use data expiration to help clear out data that is no longer being used. However, you can still sometimes have memory issues when you are using a cache, and we described about how eviction policies can be used to make room for new data. Finally, we looked at the cache-aside pattern, to make sure your most common data is stored in a cache to help speed up the time required to retrieve it.

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources that you leave running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Check your knowledge

1.

What happens if a command in a Redis transaction fails?

2.

Which of the following is a Redis command for managing data expiration?

3.

Your Redis cache is configured with the volatile-ttl eviction policy. If it runs out of memory and you try to insert a new key, which existing key is removed?