Understanding Modern Trade-off Analysis in Software Architecture
summary
Compares two concrete patterns for order/payment/inventory: hydrate full payload (one DB access, better scalability, but causes stamp coupling, contract versioning and bandwidth waste) versus pass IDs only (multiple DB reads, better consistency, simpler contracts). Gives a starter toolkit: five disintegrators (functionality, volatility, scalability, fault tolerance, access restrictions) and three integrators (transactional boundaries, data dependencies, workflow), recommends qualitative then quantitative analysis with architectural fitness functions, and frames decisions as choosing the least worst design.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 1:30Session "Understanding Modern Trade-off Analysis in Software Architecture" by Neal Ford
- 50:37Neal answers questions from the audience
- 54:37Outro
related talks
33mFrom Enterprise Architecture to Software Design - Critical Thinking
57mSoftware Architecture: The Hard Parts
44mDeliberate Architecture
54mArchitecture Foundations: Styles & Patterns (2021)
01h 00mPatterns for Software Architecture
52mMeta modern Software Architecture
41mArchitectural Thinking
42mHigh-Speed DDD (revisited)