← Path
Microservices Architecture · Microservices Boundaries: Bounded Contexts and Service Design
0 XP- 1 current stop: learning
- 2 upcoming
- 3 upcoming
- 4 upcoming
- 5 upcoming
Finish after stop 5
Stop 1 of 5 · Ticket office on Market Street
Trick to keep in mind+3 XP
When one word means two things to two teams, you have just found a boundary.
Inside a bounded context every term has exactly one meaning and one model, and the team's shared vocabulary is its ubiquitous language. Outside it, the same word can honestly mean something else. Sales, entry and support all say ticket, so each keeps its own small model rather than forcing one oversized class on everybody.
Read it once, then a question tests whether the trick stuck.