The State of Infrastructure-From-Code 2023
summary
Claims that tools analyze application code and automatically produce deployable cloud stacks, inferring resources, VPCs and least‑privilege policies rather than requiring hand‑written templates. Examples include generates API Gateway Lambda and Redis cache with VPCs and IAM policies and approaches named are SDKs, new languages, annotations or hybrids. Tradeoffs are concrete: SDKs lag cloud features, annotations need huge analysis, languages force hiring, and many tools integrate with Terraform or run as SaaS. One data point: 63% of engineering capacity goes to feature work which motivates adoption.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:58Infrastructure-from-Code vs Infrastructure-as-Code
- 3:22Problems solved
- 4:26Four IfC approaches
- 7:54Tool comparison dimensions
- 11:03Role of Infrastructure-from-Code in existing teams
related talks
19mInfrastructure as Code: A Must Know Skill for Today's Developers
32mInfrastructure From Code: Next up for DevOps?
42mInfrastructure as Code - Lessons learned from Dev to Ops
21mPitfalls of Infrastructure as Code (And how to avoid them!)
33mScaling Infrastructure as Code
01h 02mTools and Techniques for Infrastructure as Code
46mImplementing Infrastructure as Code
44mInfrastructure as Software