Skip to main content

A happy story of migration from on-premises to Microsoft Azure

When we say cloud, our mind is flying to scalability. Yes, this is the beautiful of cloud. In the last period of time I had the opportunity to work on a project that needs to scale from 2-4 instances to 200-300 instances in a few hours. The peek is pretty short (2-4 hours)
In this kind of moment you realize how hard would your life be be if you would not have load balancer and traffic manager. On on-premises solutions I see almost every month a possible issues reported by customers or external team that load balancer is not behave as expected. Testing a load balancer is pretty hard when you need to simulate 20k-50k clients with different IPs and configurations – and also very expensive.
Next, you realize that using only one data center is not a good idea, you want to be protected if something happens with that data center. Not only this, but because of the client business, we could easily group the load in 4 geographical regions (America, Europe, Asia and Australia). Because in this moment we don’t have a data center in Australia, we decided to go only in 3 data centers and in future will see :-).
With Traffic Manager it will be extremely easy for us to redirect client request to exactly the data center that has their data, without having to redirect them to another nodes(in 80% of cases this should be applicable for us).
What next? Additional to this, we need a mechanism to cache clients request until our instances are ready. For this purpose, Azure Service Bus is ready to help us. Once the command is send to our system, clients subscribe to Service Bus and wait a notification from backend. Also we are using Azure Service Bus to distribute the work to multiple instances.

And yes, we were able to migrate a system from on-premises to cloud with only a few modification. The legacy part of the system was not modified and works great. This is the beautiful of Microsoft Azure.

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…