Skip to main content

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

By
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.

Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

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

By
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.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more