Part 8 of 8 · 3 min read
Exercises
Easy
Easy 1: Shared or hidden (20 minutes)
A hotel has reception, housekeeping and billing. List five facts for each. Mark each fact as shared with another context or hidden, with a reason.
Done when: three lists of five, each fact marked.
Hint
A fact is shared if another context cannot do its job without it.
Easy 2: Same word, two meanings (20 minutes)
Find three words that mean different things to two parts of a business you know, such as "order", "account" or "release". Explain each difference in one sentence.
Done when: three words with two meanings each.
Hint
Ask two people from different teams what the word means.
Easy 3: From data to capability (20 minutes)
Turn these table names into capability names: Invoice, Shipment, Seat, Playlist.
Done when: four capability names, each starting with a verb.
Hint
Think "issue an invoice", not "invoice table".
Medium
Medium 1: Redraw a data-first design (30 minutes)
A library has services named Book, Member, Loan and Fine. Redraw it as capabilities and count the calls needed to lend a book in each design.
Done when: two diagrams and two call counts.
Hint
Count calls between services, not within one.
Medium 2: Actors and actions (30 minutes)
Run the actors and actions method on a food delivery app with three actors. List at least nine actions and group them into components.
Done when: an actor list, an action list and a grouping.
Hint
The system itself is an actor for jobs that no person triggers.
Medium 3: Characteristics check (30 minutes)
Take your Medium 2 components. Pick two characteristics from Level 0. Find one component that needs a different level from the rest and decide whether to split it.
Done when: a table of components by characteristic and a split decision.
Hint
Look for a part with a very different load or a much higher need for uptime.
Hard
Hard 1: Nested or top-level (45 minutes)
A retail company has a warehouse context with three capabilities. Show how your answer changes with one team, three teams, and three teams in different countries.
Done when: three setups, each with a decision and a reason.
Hint
BM lets team structure decide.
Hard 2: Find the wrong boundary (45 minutes)
A system has an Orders service and a Stock service. Nearly every order change also changes stock, and they call each other 5 times per request. Diagnose it, propose a fix, and describe the cost of making the fix.
Done when: a diagnosis, a new boundary and a cost list.
Hint
Two services that change together and call each other all the time are one service.
Hard 3: Plan a safe start (50 minutes)
A team is new to a lending domain and wants microservices. Write a plan that starts with modules in one codebase, states how to tell which boundaries are stable, and lists the signs that a split is due.
Done when: a plan with at least three signs and a first split candidate.
Hint
A stable boundary is one where changes rarely cross it.