Infrastructure-From-Code and the end of Microservices
summary
Claims that Infrastructure-from-Code compilers read plain application code with small annotations, infer resources and permissions, and emit Pulumi/terraform artifacts. Demo compiles a Node/TypeScript OCR app where persist and expose annotations turn an in-memory map and local route into a persisted Redis/Dynamo store and public API, then compiles to AWS Lambdas or EKS services. Research cited shows only ~63% of engineering time remains for features in distributed systems; production IfC runs ~1.5 years and supports multi-service async deployments.
AI-written summary · about
chapters (8)
- 0:00The case for new architecture
- 1:59Microservices vs monoliths
- 6:17What is adaptive architecture?
- 9:35Infrastructure from code
- 12:33Live demo and implementation
- 27:15Demonstrating adaptivity
- 34:49Comparison and takeaway
- 41:36Q&A and conclusion
related talks
20mInfrastructure as True Code with Pulumi
29mInfrastructure as Software
27mApplication-Driven Infrastructure
23mUnleashing Potential Across Teams: Infrastructure as Code
33mScaling Infrastructure as Code
36mInfrastructure as Code Done Right: Discovering and Fixing Common Missteps
53mInfrastructure as code - is it really?
15mInfrastructure as a Code: Best Practices and Myths