Road-movie architectures
summary
Claim: chasing a single homogenized “target architecture” repeatedly multiplies complexity and fails. Evidence: organizations hit thousands of live systems (one cited CIO reports 9,000), one insurer shows 35 policy systems with the oldest live since 1974. Recommended alternative is minimal well-documented APIs and fallbacks (REST/GraphQL/gRPC, message buses, file transfer/batch) to enable integration within a day like Stripe and to design for construction for deconstruction with a bold benchmark: shut down in a single day or in small iterative steps.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:51Problem with target architectures
- 10:21Road movie architectures concept
- 13:07Three key properties
- 21:37Designing collaborative systems
- 28:23Traveling light and deconstruction
- 34:48Topical and flexible systems
- 41:51Managing existing systems
- 43:16Summary and closing thoughts
related talks
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
27mArchitecting for Change Debate
50mThe Unbearable Weight of Architecture
42mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
39mMinimal Viable Architecture
44mThe Art of Architecting for Scale
27m“Good Enough” Architecture Part 2
01h 00mPaved Roads - Architecting for Distributed Teams