Skip to main content

Azure Websites–Staged deployment

One advantage that the traditional Azure Cloud Services had over Azure Websites was the support for VIP swap. This allowed you to switch your development and production environment with one click. You could deploy your application first to the test environment, check if everything is working as expected and then switch to production. The only difference between the 2 environments is that one is using the ‘real’ url of your cloud service where the other is using an auto generated GUID.

If you wanted a similar experience using Azure Websites, you had to deploy to multiple sites. This has now changed thanks to the introduction of Deployment Slots.

From the documentation:

The option to create site slots for Standard mode sites running on Microsoft Azure Web Sites enables a staged deployment workflow. Create development or staging site slots for each default production site (which now becomes a production slot) and swap these slots with no down time. Staged deployment is invaluable for the following scenarios:

  • Validating before deployment - After you deploy content or configuration to a staging site slot, you can validate changes before swapping these changes to production.

  • Building and integrating site content - You can incrementally add content updates to your staging deployment slot, and then swap the deployment slot into production when your updates are completed.

  • Rolling back a production site - If the changes swapped into production are not as you expected, you can swap the original content back to production right away.

Microsoft Azure warms up all instances of the source site slot before the swap to production, eliminating cold starts when you deploy content. The traffic redirection is seamless, and no requests are dropped as a result of swap operations. Four deployment slots in addition to the default production slot are supported per Standard web site.

Each deployment slot has its own publish settings, so the deployment experience in Visual Studio using Web Deploy remains similar(and also Source Control Integration is still an option).

image

More information here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more