Reading diagrams / Topic 20 of 42
Stations: what each entry touches
The rule
Each entry's path runs from its opening to a short reply bar on the right. Along the path, a ring marks a station: code that touches a resource. Beside it are the verb and the table, such as “read notes” or “delete notes”.
A hollow ring reads. A filled ring writes. The head of the opening repeats the answer for the whole entry: solid if anything on the path writes, hollow if it only reads.
Blue lines join the rings to the database in the rack. The table names under the database are every table the program touches. Small dots on a path are calls; a later lesson uses them.
A ring's colour is its resource. Blue rings touch the database. A violet ring on a path means the entry reaches the language model, and an orange ring means it reaches the network; neither names a table. In review-desk, both sit on the /reviews/run path.
Under each resource in the rack, a count says how many entries reach it: “reached by 5” under policy-docs' database is all five of its entries. The more entries reach a resource, the larger it is drawn.
- Solid head: the entry writes. Hollow head: it only reads.
- A ring labelled with a verb and table confirms that access; no such ring on the path rules it out.
- Violet ring: the entry reaches the model. Orange ring: the network. No ring of that colour on the path rules it out.
- The count under a resource, such as “reached by 5”, is how many entries reach it.
notes-api.
Loading the system map.
policy-docs: a service that stores documents behind access policies.
Loading the system map.
review-desk: a small service with two routes. Its purple hull and the green box at the bottom of its wall are later topics.
Loading the system map.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.