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

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP