Zero downtime deployments have been a necessity for SaaS solutions for quite some time. But with the growing adoption (and resulting expectations) of cloud-based solutions, the availability and flexibility of zero downtime deployments is now being sought for non-SaaS solutions as well.

I've been solving the challenges of zero downtime deployments for solutions hosted in private data centres, for solutions hosted on IaaS, and for solutions hosted on PaaS. In this talk, I want to share some of that experience with you, and I want to do it in the context of Azure PaaS. I'm not going to dive into Kubernetes-specific mechanisms. I'm also not going to focus on Azure Container Apps. The background will be services like Azure App Service or Azure Functions.

Join me to understand the zero downtime deployment capabilities Azure provides for these services, what requirements they place on an application, and what aspects of an application they can't handle. Starting with these capabilities, we will walk through a zero downtime deployment process that includes elements of a broader picture, such as database or background workers. You will leave with an approach that you can reuse or adapt to a different context.