From Anti-pattern to Pattern Driven Architecture Definition
summary
A concrete process for reducing architectural mistakes at a 294‑person org running ~70 systems and 271 services on 2,056 servers is described: create an architecture committee, assign an architecture owner, record cross‑system rules as ADRs in git and keep project pages per initiative. The claim: this lightweight pattern yields living strategy documents, templates and project pages that force early decisions, improve transparency, track drivers and milestones, and feed continuous evidence back into the strategy so changes are validated and mistakes shrink.
AI-written summary · about
chapters (15)
- 0:00Start
- 7:59Cv Driven Development
- 8:35Track Factor of Zero
- 11:50Architecture Drivers
- 12:33Business Strategy
- 13:03User Habits
- 13:53Development Model
- 14:51Technology Trends
- 17:51Architecture Owner
- 18:57Architecture Definition Practices
- 19:36Strategy of Architecture
- 30:43Templates
- 31:27Architecture Definition Pattern
- 33:56Caveats
- 34:31Indecisiveness
related talks
16mEveryone architect!
27mSoftware Architects and Autonomous Teams
45mArchitecture and the Architect AD2022
37mArchitecting for Tomorrow: A Pragmatic Perspective
39mOne Does Not Simply Make Architecture Decisions Alone: ADRs and Architec
41mSoftware Architecture in a DevOps World
01h 00mAgile Architecture
58mRefactoring the Architect’s role