Azure Local
December 29, 2023

Platform Engineering & Azure Local

Breaks down the differences between SysAdmins, DevOps and Platform Engineering, and how Microsoft supports Internal Developer Platforms.

This post gives a quick summary on the similarities and differences of the terms SysAdmins, DevOps, Platform engineering and after that it dives deeper into how Microsoft answers the requests for Internal Developer Platforms.

The way we create and deploy applications has changed a lot. A decade ago developers made monolithic applications and would ask the SysAdmins to deploy a physical/virtual machine to land their application on.

Even the SysAdmins would have different expertise such as Virtualization, Storage, or Networking and if you were lucky the stars aligned and they would be all available to execute your request in a timely manner. Only if the budget holder approved of course.

When the cloud era started, many of these technology silos could be avoided by developers. The cloud brought a new operating model and cloud providers delivered a self-service model with it, that enabled them to deploy the infrastructure themselves to host their application.

The term 'DevOps' was brought to the stage as the operational part was taken away by the traditional SysAdmin and the developers became responsible for that part as well. Some developers were fine with that approach, others rather only kept themselves busy with developing instead of the deployment methods and managing underlying infrastructure.

Platform Engineering

Platform engineering is the upcoming term for the practice of building a platform that is specifically meant to make developers' lives easier. It's not built specifically by DevOps engineers, developers or SysAdmins but 'Platform engineers'.

From SysAdmins and DevOps to platform engineering

The ultimate goal of Platform engineering is providing developers the best experience and productivity by providing self-service capabilities with automated infrastructure operations. Depending on the platform of choice the actual work that needs to be done on the platform differs. Some platforms offer a turn-key approach while with others you'd still need to get your hands dirty and install Kubernetes (for example).

Platform engineers provide an integrated product most often referred to as an “Internal Developer Platform” covering the operational necessities of the entire lifecycle of an application. Depending on the chosen platform it can support those developers still in the traditional application development, developers dipping their toes in containerization, or cloud-native developers.

Keep an eye out for the supportability of the platforms by the vendors, depending on the level you expect from your platform you can mix and match your solution. If you want to deliver PaaS services to your internal organization and make use of an open-source PaaS solution, it is harder to get support when it breaks than when using a fully integrated PaaS platform.

Azure Local

Microsoft's efforts in providing an answer date back to 2013, when Windows Azure Pack was launched, the predecessor of the current Azure Stack portfolio. Azure Local (formerly Azure Stack HCI) provides a platform that enables IaaS and PaaS capabilities on any physical location. The IaaS and PaaS services are the same services that you are used to and consuming when using Microsoft Azure and provide the same functionality. As the platform is connected with Microsoft Azure using Azure Arc, we make use of the management layer of Microsoft Azure to manage and interact with the platform and the services on top. That also means that the platform and services, which can run anywhere, are visible and manageable the same way from the Azure Portal or CLI as PaaS services running in a Microsoft datacenter. The fully integrated cloud approach of the platform satisfies the requirements for an Internal Developer Platform; "providing developers the best experience and productivity by providing self-service capabilities with automated infrastructure operations".

Developers can develop their applications as they always have done. Azure Local provides full self-service capabilities through Microsoft Azure's API layer which supports Infrastructure as Code (IaC). Developers can create pipelines with the same underlying code, the deployment destination is just a parameter in the deployment. Because of the integration with Azure, you can also benefit from of all other features that Microsoft has developed for Microsoft Azure, for example Role-Based Access Control (RBAC) based on Microsoft Entra ID or security analytics using Microsoft Sentinel.

By using Azure Local you're bringing a piece of the Microsoft cloud to your own location, including cloud services.

Microsoft Azure services available for Azure Local include:

  • Virtual Machines
  • Azure Kubernetes Service (AKS) - (Managed Kubernetes)
  • Azure Virtual Desktop - (Desktop and app virtualization service) -> Learn about Azure Virtual Desktop benefits
  • Azure App Services - (Web Applications)
  • Azure Functions - (Serverless compute service)
  • Azure Container Apps - (Serverless container service)

In summary, Azure Local is an ideal fit for platform engineering because it provides a flexible, scalable, and powerful platform for building and deploying hybrid cloud solutions that can support a wide range of workloads and use cases.

Learn more about Azure Local and the services available or get in touch!

Let’s talk it through

One conversation is usually enough to see where the value is for your organization, whether that’s in cost, risk, or everyday management. No slides required.