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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Azure Well-Architected AI workload Assessment

By
  AI is everywhere, part of the IT solutions we build and run today. Having an AI service, a good model, and data is not enough. As for cloud, the real difference is how we build, manage and run the whole solution. Microsoft created the Azure Well-Architected Framework for AI Workloads exactly for this reason — to help teams design AI systems that are reliable, secure, and cost-efficient. The assessment has six main categories that we cover in the next section. Based on the results, we can gain a good understanding of the current AI workload estate and a list of actions to improve how you run and manage your AI workloads . Designing the AI Application The first step in building your AI application is to consider how you will structure it. Using containers for tasks like data processing or model inference helps maintain consistency across the system. This approach makes it easier to update, move, and manage different components. When you have multiple steps in your workflow, such as...
Post a Comment
Read more