Website to share content for the O'Reilly book Infrastructure as Code, whose topics include cloud architecture, infrastructure design, infrastructure codebase management, infrastructure delivery lifecycle and workflows, infrastructure automation tools, infrastructure platforms, and infrastructure orchestration. Composable infrastructure is a particularly recommended approach. The site includes guidance, principles, patterns, practices, examples, and techniques.
The question running through the Future of Software Development retreat: How much do we let an agent decide, and how do we stay confident in what it does?
I could have Claude Code directly create infrastructure for me. But I prefer to have it write infrastructure code, for consistency, confidence, and composability.
Agentic software engineering looks familiar to me. We'll manage systems that produce, deliver, and operate software, including infrastructure code. How do we govern how agents build a system? Do we give no guidance ("vibe coding")? Do humans manually inspect every line ("humans in the loop")? Or do we build systems that shape both outcomes and behavior ("humans on the loop")?
DevOps removed the wall between developers and operations, but the wall between developers and infrastructure remains. The next generation of infrastructure automation will use AI to remove that wall by embedding into the software developer's workflow.
An approach for identifying what value organizations get from digital infrastructure and how to trace that to the specific infrastructure delivery capabilities.
Can software delivery be made more effective by moving beyond current IaC tools to give software developers a friendlier, more effective interface for defining and provisioning infrastructure for themselves?
In January I set up an “Infrastructure Effectiveness Survey” and asked people to fill it in, promising that I’d share what I learned from it later on. Later on has arrived!
The idea that you can trade speed and quality off of one another is false. The quality x speed quadrant illustrates that the goal is to use quality and speed to reinforce one another.
An infrastructure management team is not as effective as an infrastructure platform.
Infrastructure as Code was supposed to bring an end to snowflake servers. It hasn't.