On Day Two Cloud we’ve had a lot of discussions over using infrastructure as code, especially when it comes to the cloud. We’ve looked at solutions like Ansible, Terraform, the AWS CDK, and Pulumi. Which begs the question, which IaC solution should you learn? Does it matter what you already know? Does it matter how your organization is structured?
Should we even be talking about IaC and not IaS or IaD? Ned and I decided to sit down and have a chat, I hope you enjoy it. If you’ve got thoughts, hit us up on Twitter or join the Packet Pushers’ Slack.
- The different approaches to Infrastructure as Code (IaC)
- Terms including IaC, DSL (Domain-Specific Language), GPPL (General Purpose Programming Language)
- Pros and cons of each approach
- Other tools
- Whether you can do IaC with one tool
Build applications with Linode’s simple cloud manager, API, or CLI. Quickly scale up or down with standard VMs, dedicated CPUs, and enterprise-grade GPUs—all with the best price-to-performance and same pricing across eleven global data centers. You also get fast, human support 24/7. Visit Linode.com/day2cloud and get $100 in free credit to try them out.