Before we understand the concepts of moving the data or application into azure, the most important is understanding what it takes to move the data or application into cloud, which is building an infrastructure for the organization. In the unit of AZ 305, Design Infrastructure Solution, we learn about the design strategies for building the infrastructure for the applications or data to shift their base into cloud. The infrastructure solution consists of the following major activities –
- Design an Azure Compute Solution
- Design an application architecture
- Design network solution
- Design Migrations
Compute refers to the hosting model for the computing resources that your applications run on.
Following are the different compute services that azure provides –
| Azure Service | Purpose |
| Azure Virtual Machine | Deploy and manage virtual machines inside an azure virtual network |
| Azure Batch | Apply this managed service to run large scale parallel and high performance computing applications |
| Azure app service | Host web apps, mobile back ends, Restful APIs, or automated business processes with this managed service |
| Azure Functions | Use this managed service to run code in the cloud, without worrying about the infrastructure |
| Azure Logic Apps | Configure this cloud-based platform to create and run automated workflows similar to capabilities in Azure Functions |
| Azure Container Instances | Run containers in azure in fast and simple manner without creating virtual machines or relying on higher level service |
| Azure Kubernetes Service | Run containerised applications with the managed Kubernetes service |
WHICH COMPUTE SERVICE TO USE?
When deciding on which compute service we should be using for the task present, there are following considerations that need to be taken care of –
Control – Determine if you require full control over installed software and applications
Workloads – Consider the workloads you need to consider, such as HPC Workloads or event driven workloads
Architecture – Think about what architecture best supports your infrastructure, including micro service, full fledged orchestration, server less.
When migrating we need to analyse –
Cloud optimised – To migrate to the cloud and refactor applications to access cloud native features, consider compute services that are cloud optimised.
Lift and Shift – For lift and shift migrations, consider applications that do not require code migrations.
Containerised – In your migration planning, consider whether your compute service needs to support containerised applications or COTS apps.
HOSTING
Azure offers three hosting for its users –
- IaaS – This is the infrastructure as a service. In this case, you can create individual virtual machines along with associated networking and storage components. So, here although Microsoft does provide the infrastructure, it is the job of the company to handle it.
- PaaS – This is the platform as a service. In this case, a managed hosting environment is provided for setting up your website, or app. These include azure batch, azure containers, app service and azure kubernetes.
- FaaS – This is function as a service. In this case, you don’t have to worry about even the hosting environment. Here, you deploy the code and the service automatically runs it! Azure functions and logic apps are part of this.
In the end in the following page, you will find a beautiful design for choosing the correct azure compute service.
https://learn.microsoft.com/en-us/training/modules/design-compute-solution/2-choose-compute-service
Foolishly Yours,
Avantika/Anmol

Leave a comment