From the Blogosphere
Azure Resource Manager | @CloudExpo #IaaS #Azure #ASM #ARM #AWS
One of the key tenets of cloud, especially infrastructure services, is programmability
By: Janakiram MSV
Sep. 20, 2016 07:00 PM
Azure Resource Manager: The Shift from Services to Resources
In the first part of this series, we discussed the evolution of Azure IaaS and role of Azure Resource Manager. The next installment of the series explains the key differences between Azure Service Management (ASM) and Azure Resource Management (ARM) models. We will also take a look at key concepts and terminology related to ARM.
ASM or ARM?
One of the key tenets of cloud, especially infrastructure services, is programmability. Almost every cloud provider exposes a set of APIs to manipulate the virtual infrastructure programmatically. Even before the Cloud Computing term became a buzzword, Amazon exposed APIs for storage and compute, which eventually became the core of AWS.
When Microsoft built Azure, developers could interact with the control plane through the Azure Service Management (ASM) API. Before officially supporting REST, ASM was exposed as a set of SOAP endpoints. Given the smaller set of services based on storage, compute, and application services, ASM was good enough for developers and third-party ISVs to talk to Azure. Eventually, as new services got added to Azure, the API footprint expanded proportionally. When the partner ecosystem started to develop tools for Microsoft’s public cloud platform, ASM became the core of Azure. Even today, ASM is extensively used by ISVs like CloudBerry Lab and Cerebrata. Microsoft started shipping language bindings, native SDKs, and command line tools that heavily relied on ASM.
Since ASM was the API facade for the first version of Azure IaaS, it suffered from the same limitations and constraints. Resource provisioning was not cohesive and offered no support for atomic deployments and rollbacks. Developers had to deal with a disjointed set of APIs to provision resources that logically belonged to the same workload.
The original Windows Azure Management Portal was built on top of ASM. With the introduction of Azure IaaS V2, Microsoft introduced a new portal that aligned with the ARM strategy. To differentiate these two interfaces, Microsoft started calling the old portal as the classic portal. Some of the resources such as VMs that are provisioned through the classic portal also derived the moniker of Classic VMs.
Read the entire article at The New Stack.
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week