Drill
Across the module line
Five pull requests are up for review and two modules talk constantly. Sort the pull requests, then judge the split plan.
3 minMediumMembers lesson
Membership isn’t open yet. The free lessons are open — 18 of them.
What you'll be able to do
- 1Predict which changes to Checkout break a module boundary — a query joining another module's table, a call into another module's internals — and what that costs when the module is later moved out.
- 2Predict whether a proposed split will become a distributed monolith from its call pattern, shared data and deploy coupling — chatty calls, cross-service transactions, lockstep releases.
Inside the lesson
- steps
- 2
- questions
- 2
- simulations
- 0
Step 1 · The setup
A travel site runs one deploy, four modules: search, bookings, payments, loyalty. Five pull requests are up for review this week, and the boundary log shows bookings and loyalty calling each other about 40 times per booking. Next quarter's plan: make every module its own service.
Step 2 is for members