1 Step 0 — What the tutorial is about
Step 0 contains no code. It states the subject: not ROT13, but the architecture around it. The functionality stays almost unchanged for 81 steps, which is what makes the changes around it visible.
Two rules are set here and hold for the whole tutorial:
Meet each solution only after you have experienced the problem it solves.
That is why the tutorial does not start with MQTT, and not with dynamic subscriptions either. It first builds a system with deliberately awkward mediators, puts it into operation, and only then asks whether they have earned their place.
The second rule is about vocabulary: Intent, Status/State and Event are named only after they have been used. They appear in the tutorial around step 42, not before.
The planned route, from step 0:
direct method calls → egoistic services → mediators → separate processes
→ filesystem as transport → Syncthing → "why all these mediators?" → rewind
→ services subscribe themselves → dynamic wiring → across processes
→ across Syncthing → when a mediator IS useful → MQTT
1.1 The three questions
The wording of the three questions matters, and it is easy to replace it with something weaker:
| The tutorial asks | A weaker version |
|---|---|
| Who knows whom? | who communicates with whom |
| Who owns what? | which data each part holds |
| Who decides how the system is wired? | which part connects everything |
“Knowing” is not “communicating”: two components can exchange messages all day without either one naming the other. “Deciding the wiring” is not “connecting”: the part that forwards messages need not be the part that chose the route. Both distinctions become concrete later — the first already in step 1, the second in part III.