Deliberate Architecture
summary
Industry demographics produce many inexperienced hires and a high churn rate so the claimed developer half‑life ~3.5 years forces architectures that survive personnel turnover. Software qualities like performance, security and usability qualities are emergent nonlinearly from features, so choices (microservices, layered monoliths, serverless, REST) trade measurable attributes: deployability, operability, latency, maintainability. Use Grady Booch’s forces model, Roy Fielding’s REST ideas, TDD, ensemble programming, and monitor in production to shape architectures so desired qualities appear rather than hoping fashion will deliver them.
AI-written summary · about
chapters (5)
- 0:00Start
- 36:32Factoring incident forces
- 41:06Inputs (Requirements)
- 49:27dynamical non-linear systems
- 57:59Functionality is independent of structure
related talks
59mDeliberate Architecture
44mDeliberate Architecture
58mThe past, present and future of Architecture
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
01h 03mEvolutionary Software Architectures
45mArchitecture: The Stuff That's Hard to Change
45mKeeping Up with the Times: Flexible Architectures
01h 03mLong-lived software architectures that survive decades without debt