Thinking Beyond IaC:an OSS Approach to Cloud Agnostic Infr...
summary
Claims that Infrastructure from Code (IfC) infers required cloud resources by analyzing application code and provisions them automatically. Demo uses Nitric (Python SDK + local simulator) to deploy an OCR app that calls Google Cloud Vision and, when run with Pulumi, creates about 62 GCP resources (Cloud Run, API Gateway, buckets, key‑value store, service accounts). Local dev works via nitric start; nitri up provisions the cloud stack. Promised outcomes: faster prototyping, fewer infra pipelines, and reduced configuration drift.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:50Session agenda
- 2:56History and evolution of infrastructure as code
- 9:49Challenges with infrastructure as code
- 14:28Infrastructure from code
- 20:56Nitric SDK demo
- 32:12Nitric app demo
- 38:36Deploy to Google Cloud
- 41:47Key takeaways
- 45:14Q&A
related talks
29mUnleashing Potential Across Teams: The Power of Infrastructure as Code
25mThe IaC Tooling Face-off for Modern Cloud Native Ops
39m.NET: Infrastructure as Software
24mThe OSS IaC Tooling Face-off for Modern Cloud Native Ops
12mCloud = Application Enablement and Innovation ≠ IaaS
09mInfra-like-apps - GitOpsifying Cloud Natively Managed Infrastructure with...
31mCloud Programming Languages and Infrastructure From Code: An Empirical Study
08mInfrastructure as code in any programming language