Application Resilience - Whose Job Is It Anyway?
summary
Claim: application resilience and rapid innovation coexist only when teams adopt a shared responsibility model and concrete practices rather than slogans. The talk shows the approach: embrace failure as continuous resilience, break monoliths into microservices, run CI/CD with GitHub Actions, manage infrastructure with Terraform, and instrument with OpenTelemetry. Evidence: AWS whitepaper and published practices tie these tools to lower costs, fewer silos, and measurably higher quality.
AI-written summary · about
chapters (8)
- 0:00Introduction and Overview
- 0:19The Coexistence of Resilience and Innovation
- 1:06Cultural Transformation in Software Development
- 3:51Shared Responsibility Model
- 5:34DevOps and Continuous Improvement
- 7:00Technical Considerations for Shared Responsibility
- 9:18Continuous Integration and Delivery
- 11:33Security and Final Thoughts
related talks
51mWithout Resilience, Nothing Else Matters
05mBuilding resilience in our organizations...
22mResilience Is Not Enough
06mCan Resilience Engineering be sufficiently described in 5...?
58mResilient by Design
01h 05mKeynote - Without Resilience, Nothing Else Matters
16mResilient by Design: Architectures for Crisis Response & Recovery
34mToward continuous resilience