cloudpatterns.appClassroomKatasWhiteboardBlog
Architecture LineLesson

Service boundaries: where to cut

Checkout is moving to services, and the first plan cuts by layer — web, logic, data. Why does every feature then need all three teams, and what does a better cut follow? Business areas with their own words and data, things that change together kept together, one owner for each piece of data — and teams set alongside the lines.

14 minMediumStation: Service boundaries

Members lesson

Membership isn’t open yet. The free lessons are open — 18 of them.

Start a free lessonSee the path
  1. Monolith
  2. Modular monolith
  3. Service boundaries
  4. Microservices
Architecture Line — where this lesson sits

What you'll be able to do

  1. 1Choose service boundaries for Checkout by business capability and bounded context rather than by technical layer, and say which data each service owns.
  2. 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.
  3. 3Explain how team structure shapes service boundaries (Conway's law), and why boundaries and team ownership should be set together.

Inside the lesson

steps
14
questions
12
simulations
0

More on the Architecture Line

  1. Monolith: one deployableOpen14 min
  2. Modular monolith: boundaries inside one deployMembers15 min
  3. Microservices: what the network costsMembers17 min