Member-only story
Infrastructure-as-Code —A Hype or a Game-Changer?
A Machine Learning Engineer’s perspective of Terraform
As a Machine Learning (ML) engineer, I’ve done many projects with various forms of infrastructure, but most are either hybrid or fully cloud-based. In all these projects, I’ve always found it frustrating that these cloud-based infrastructure were managed via custom scripts or using the graphical user interface (GUI)*. It was hard to manage these ultra-long scripts, and even harder to keep track of all the resources that the team has setup by hand via the GUI.
As such, I decided to put Terraform on my list of “Technologies to learn in 2022”. For context, Terraform is one of the most popular open source tools for infrastructure automation, also known as Infrastructure-as-Code (IaC).
Adding an IAC tool to my arsenal was my goal as I wanted to understand first-hand why people advocated for it and whether the added complexity to the stack would be worth it. To a certain extent, the engineer in me simply wanted to codify and version the sh*t out of everything 🙂.
So after spending the last few weeks picking up Terraform, here are some of my initial thoughts and learnings about it.
