Drill
Split it to clean it?
Cart keeps breaking payments' tests, and the plan is to split into services. Check the plan, then pick the move.
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 of a struggling monolith's pains a split into services would relieve — deployment ones (a shared release, scaling everything, one team blocking another) — and which it wouldn't — structure ones (tangled code with no boundaries).
- 2Choose between modularizing Checkout inside one deploy and splitting it into services, from team count, release pain and how settled the boundaries are.
Inside the lesson
- steps
- 2
- questions
- 2
- simulations
- 0
Step 1 · The setup
A bookshop's app is one deploy shared by three teams, and its weekly release goes out without fuss. But cart changes keep breaking payments' tests — cart code reads payments' tables directly in about 30 places. The plan on the table: split into cart, payments and stock services.
Step 2 is for members