Infrastructure from Code: What Happened and What's Next
summary
Infrastructure-from-code promises write-app-and-run, removing YAML and context switches, but seven early vendors show the outcomes: two of seven startups fold while Nitric and Encore adapt. Wing uses Winglang in ~20 lines to wire a 2-minute timer, cache read/update, and queue; Clo uses JavaScript annotations to generate deployable IaC. Failure traces to vendors taking control, inflexible abstractions, and mismatched “best practices” for compliance. Next stage is AI-driven, observable, adaptable infrastructure that monitors live usage and recommends swaps (containers ↔ serverless) while keeping platform teams in control.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 1:51What infrastructure from code promised
- 4:22Why infrastructure from code failed
- 13:15Examples of IFC tools
- 17:30Lessons learned from IFC
- 19:59The future of adaptable infrastructure
- 24:58Summary and Q&A
related talks
23mThe Agentic Infrastructure Gap: In-Distribution Languages Make It a Coding Problem
19mWrap: What To Build Next
16mNothing.
37mCode is cheap. Now what?
36mAI's Disruption of Infrastructure Operations
38mThe 'outer loop' is dead: How AI and cloud development will revolutionize DX
36mDeveloper Experience Trends & Predictions
28mWhat Handcrafted Servers Taught Us About Handcrafted Code