It's no secret that security is vital for different areas of an Episerver website, especially the editing and admin interfaces. If you use Azure Active Directory to login to organization infrastructure already, why not use it to secure your website? Optionally, you can use Azure AD to shield non-production environments from public view entirely, allowing you to develop new features and content without the public's eye on them.
In web applications, including Episerver applications, leveraging cache properly is crucial to the performance of your site. As a developer, you will have a number of different types of cache available to you. They all have different purposes, lifecycles and storage locations so it's best to know how and when to use them.
Over the past years working with Episerver, a common conversation I've found myself in is where someone is having trouble reliably deploying their application. It can be represented in a number of ways, but it usually comes down to:
1. Long Deployment Routines
2. Unexpected Behavior
3. Slow Deployment Cycles
4. Interruption in Availbility to end-user