Infrastructure as Code on Azure - IaC - Part2
Hello Everyone, This is the second article on Infrastructure as Code on Azure series. In this article, we will learn about different IaC tools and their basic functions. Let's get started.
Before we get into the details of IaC tools, it is important to understand the Declarative vs Imperative approach and the differences between these.
Declarative vs Imperative Approach: Declarative state is the process of dictating the desired results. For example, with the help of the IaC tool, we can dictate our desired state by defining the required resources, their configurations, etc. This approach of programming language works on “what” will be our desired state, in contrast, the Imperative approach defines that “how” the desired state can be achieved. Usually imperative approach of code contains a set of commands.
IaC Tools: IaC tools can be further divided into two categories. Configuration Management and Provisioning or Orchestration tools. Below is the list and comparison of well-known IaC tools and their brief description.
IaC in DevOps: DevOps is all about bringing IT Operations and Development teams together to shorten the Software Development Life Cycle – SDLC and provide continuous delivery. Infrastructure as Code is a key DevOps practice and helps with continuous delivery. IaC enables DevOps teams to provision new environments, similar to their productions ones, and helps in testing and resolving issues before going live.
Recommended by LinkedIn
That’s it for today. In the next article, we will provision few resources in Microsoft Azure using IaC.
About me: I am a Microsoft Azure Certified Architect with over a decade of experience in Microsoft Technologies. I love to help Tech Community around the globe by translating my research and experience into LinkedIn Articles and Youtube videos.
Disclaimer: Please note these articles have been written based on my research and experience. The whole idea is to help the community to learn and grow. Neither I nor my (past, present, and future) employers and product owners/third parties mentioned in these articles accept any direct or indirect liability.
