← Expertise
Systems Architecture
We trace a change across the system before we draw its boundaries. The aim is a design where teams can name the owner of a decision and predict which parts must move together.
Design question
Where does responsibility sit?
Start with a write
Follow a representative update from intent to durable record. Separate the component that accepts a request from the one entitled to declare it complete.
Describe the seam
For each boundary, specify the meaning of an acknowledgement, the permitted delay and the behaviour when a dependency is unavailable.
Make the transition feasible
Keep an existing reader working while introducing a new writer. Give each migration step an observable completion condition and a way back.
A context map, an ownership register and a sequence of compatible changes.
Prepare your brief