Skip to main content

Multiple Staging Deployment of Azure Web Sites using Slots

How are you dealing the website management before going live with a new version? I have in mind different environments like production, testing, integration, development, persist the old version of the web site into a location that give you possibility to swap between the new one and old one if you have issues.


If you are using Azure Websites you will discover a new feature that gives you the possibility to have multiple staging environments live in the same time. Switching between them is done in real time. Before going further, you should know two things. One, we are not referring to staging environment, this is something more that staging and this feature is available only for Standard plan.
From now, you can deploy a new version of your web site into a separate slot, that is isolated 100% from the production one. There you can test how it’s behave, performance issues and so on. You can have as many slots as you want, each slot is accessible using a unique URL. Anytime, you can switch between them, putting another slot in production (swap). When a swap is done, the web site that was in production will replace the slot with is going in production. The mechanism is pretty simple, because in your slots, the websites are already loaded, resources allocated and so on. Only the DNS is changed. In this way the downtime is eliminated and no requests are dropped.
If during a SWAP something bad is happening and an error occurs, Azure will make automatically a rollback and the original version will be restored.
Be aware, you will pay for each slot that you have, like a normal website. For example if you have 2 slots (INT and TESTING) and another slot that is live, that you will pay 3 X Standard Web Sites.
When you create a new slot, you have the possibility to clone the configuration also. This is a pretty nice feature, especially when you have custom configuration in place. When you make s swap between slots the fallowing information will change:

  • Connection strings
  • General, Diagnostic and Monitoring setting
  • Handler Mapping

Also, there are other configuration that are not changed when you make a swap:

  • Publishing endpoints
  • Scale settings
  • Custom Domain Name
  • Bindings and SSL Certificates

I really like that scale settings are not swap between instances. In this way, we can have in slots normal configuration (one instance of our websites) and in production to have 10 or 20, based on our needs. Don’t forget that database connection string is changed when a swap is made. Because of this you need to change the one from slot to the production one before making a swap.
If you want to find more about this please visit http://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…