Stage 1 · Lesson 2 of 7
Trade-off analysis across teams
A decision that affects several teams rarely has a right answer. It has options, and each one costs different teams different things. Write each option down.
Note what it costs to build, to operate (keep running) and to migrate to, which team carries each cost, and what it rules out later. Compare every option against the same criteria, and include doing nothing as an option. The usual advice is to the organisation already runs well.
Each new database or platform adds duty, upgrades and knowledge that only a few people hold. , next, is a special case of this same analysis.
Common trapjudging options only on the build effort of the team proposing them, while the operating cost lands on another team that was not in the room.
A question to check yourself, an AI practice session and 2 cheat sheet entries come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- CoursePaidSystem Design Patterns: From Fundamentals to Real Systems
Design Gurus · Intermediate · Subscription
The distributed patterns behind most designs, to judge proposals from other teams
- GuideFreeMartin Fowler's Website
Martin Fowler · Intermediate
Free, clear writing on architecture styles, microservices and evolving designs