Infrastructure as Code (IaC) is a family of design principles, not just a technology. That’s why we designed Digital Rebar around reusable and stackable modules that treat your infrastructure automation as code.
Can adopting Infrastructure as Code (IaC) help your business? It sure can, and Rob talks about this on TFiR. Looking for more info? Check out Rob’s Post about the Business of IaC.
As technologists, we love to talk about Infrastructure as Code (IaC) as a technology [here’s Rob’s IaC talk]. However, focusing on the tech ignores the significant business value behind the concept. Why should CIOs, CTOs and even CEOs demand their teams pursue IaC practices? And why IaC instead of CI/CD, Site Reliability Engineering, or DevOps?
Paul Delory lays out a comprehensive view of all the components in the flow required to deliver applications into production.
“IT teams want to be able to provision bare-metal servers as if they were code…. Achieving that goal, however, should not require IT organizations to hire a site reliability engineer (SRE)” Read the full DevOps.com article.
We’ve been making the most basic aspects of infrastructure too complex and hard to automate. Companies can address security by building secure automation processes from the ground up.
45 minute presentation about How Infrastructure as Code Architecture influenced Digital Rebar Infrastructure as Code (Iac) is marketed as the answer to all automation problems. How can that be true when no one really has a good definition? Let’s fix that! This talk captures ideas from a tweet battle started when Rob asked for a