Architecture decision making
summary
Argues that architecture decisions start by exploring the problem space, not by Googling solutions; uses API versioning as a worked example with a three-minute exercise and three walkthroughs (shallow, time-boxed, holistic). Runs a proof-of-concept against the tech stack, weighs five solution families (path, query, media type, header, subdomain), and stresses testing, maintenance, deprecation windows, docs (Swagger), and client transition rules. Recommends a decision log, reusable code samples and using an API gateway or lightweight POC to verify reversibility and operational cost.
AI-written summary · about
chapters (6)
- 0:00Introduction to decision making
- 1:12Shallow approach to decisions
- 8:23Time-bound evaluation exercise
- 12:20Holistic approach to decisions
- 37:17Key takeaways and summary
- 38:00Q&A session
related talks
25mThinking Architecturally
28mThe lean architect: Experimenting your way to better decisions
45mArchitecture: The Stuff That's Hard to Change
58mThe past, present and future of Architecture
43mThinking Architecturally
47mMaking architecture decisions, the Agile Way
50mTowards an Evolutionary Architecture
38mAgile Architecture