Keynote: Defining and Embracing The Software Fragility
summary
Argues that fragility is measurable and reducible by concrete architecture and operations: adopt event-driven designs, centralize with an API Gateway, use message queue buffering, codify blueprints and chaos engineering to find breaking points. Recommends platform-level defaults (IAC plus policy-as-code), short‑lived secrets and tighter identity controls (zero trust) rather than vague process advice. Claims these steps increase survivability and buy time to recover, and shows practical, repeatable mitigations rather than abstract exhortations.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:29Why software fragility matters
- 5:19Safety and complexity in design
- 9:12Software fragility vs antifragility
- 12:20Attack versus protect surface
- 18:23Four fragility challenges
- 22:33Cyber incidents and gaps
- 29:58Resilient software architectures
- 34:55Antifragile systems strategies
- 41:02Key takeaways and next steps
- 42:47Q&A
- 43:51Can software be antifragile?
- 45:40Timeline for antifragile systems
- 48:09Prioritizing fixes in portfolio
- 51:22Architecture analysis tools
- 53:11Residual risks in antifragile software
- 55:19Closing remarks
related talks
01h 05mKeynote - Without Resilience, Nothing Else Matters
19mDevOps, but you don't need to be an enterprise
50mBecoming antifragile is more important than ever in disruptive times
32mSoftware security as a force of nature
33mClosing Keynote
58mBuilding antifragile systems using Secure by Design
13mKeynote: Software Security: _You_ are the Calvary
36mKeynote: The Future of Software