Part 7 of 7 · 3 min read
Exercises
Easy
Easy 1: Monolith or distributed (20 minutes)
Classify each as monolithic or distributed: one program with a database; a web app plus a separate payment service; a plug-in based desktop tool; ten services behind a gateway.
Done when: four labels with the deployment unit count.
Hint
Count the things that are deployed on their own.
Easy 2: Place the feature (20 minutes)
A shop has a "wishlist" feature. List what code would exist in each layer of a layered style, and then what one module would hold in a domain-partitioned style.
Done when: two lists, one per style.
Hint
In a layered style, a feature has a screen, a rule and a query in different layers.
Easy 3: Open or closed (20 minutes)
A report page reads data directly from the database, skipping the business layer. Is that allowed with closed layers? What is lost? Give one reason a team might accept it.
Done when: a short answer with the cost and one justification.
Hint
A closed layer forbids skipping. Speed is the usual excuse.
Medium
Medium 1: Sinkhole check (30 minutes)
Of 2,000 requests, 1,300 are pure pass-through. Compute the share. Apply the 80-20 rule. Propose two actions and their trade-offs.
Done when: a percentage, a verdict and two options with costs.
Hint
1,300 divided by 2,000 is 65 percent.
Medium 2: Modular monolith rules (30 minutes)
Design five rules for a modular monolith with modules users, orders, billing. Cover code access, data access and a build-time check. State what each rule protects.
Done when: a table of five rules with purposes and one fitness function.
Hint
A rule that is not checked by a test tends to be broken.
Medium 3: Latency budget (30 minutes)
A page makes 8 sequential calls. Locally each takes 0.005 ms. Remotely each takes 4 ms. Find the totals and the extra failure points. Say what could shrink the remote total.
Done when: two totals and a short list of changes, such as parallel calls or fewer calls.
Hint
Eight calls times 0.005 ms is 0.04 ms. Eight times 4 ms is 32 ms.
Hard
Hard 1: Defend the monolith (45 minutes)
A team of six builds a booking site for 5,000 users. A colleague wants microservices. Write the argument for a modular monolith with figures (made up) for cost, release effort and failure points, and name the signals that would change your mind.
Done when: an argument with a cost comparison and at least three trigger signals.
Hint
Do not forget cost of operations, such as monitoring and deployments.
Hard 2: Rescue a layered monolith (45 minutes)
A layered monolith takes 3 hours to deploy and breaks often. Propose a path to a modular monolith in steps. For each step state the risk, the check that proves it worked and the order.
Done when: a plan of five steps with checks.
Hint
Start with the biggest tangle and add module boundaries before splitting data.
Hard 3: Conway in practice (50 minutes)
A company has teams by skill: front end, back end, database. Releases take weeks. Describe the architecture this tends to produce, and a plan using the Inverse Conway Maneuver. Include team layout, module layout and what would go wrong.
Done when: a before and after layout and three risks of the change.
Hint
Mixed skill teams per domain are the usual target.