Ignite: Magic of Application Modeling
summary
Claims that logical application models let teams share operations as code and reason about relationships between components, with concrete examples: a MediaWiki stack wired to two MySQL instances plus memcache and HAProxy, density across 200 nodes, and tools like Docker and TLS. A concrete project models Cooper Nettie's through three iterations until components become interchangeable and models encode ops so deployments can be reproduced and understood rather than sketched as vague examples.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:40Application Management
- 0:56Density
- 1:12Scale
- 1:28Application Ecosystem
- 1:44Machine View
- 2:00Model
- 2:48Open Source Operations
- 3:04Relationships between applications
- 3:20Case study
- 3:36Cooper Nettie
- 3:52Docker
- 4:08SDN
- 4:25Interchange
- 4:40Conclusion
related talks
19mOpen Application Model: Application-centric DevOps Approach
51mApplication Threat Modeling Implementation Tips and Tricks
06mIgnite: Programming your infrastructure
50mBuilding an Application Platform: Lessons from
37mWorkshop on Defining a Reference Model for Cloud-Native Application Delivery
53mChange your tools, change your outcome
30mEverything as Code
51mApplication Stacks for the Modern World
