Location Store — where who-is-where is written down
each process writes its own address, and another process reads it to connect
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
Why no address goes into a configuration file
• Each process writes its address and the names it serves into the Store at startup, and refreshes that record while it lives. The record disappears when it stops.
• The caller reads the Store to find where to connect. Adding servers or restarting one at a different address changes nothing on the calling side.
• Which node a Spot or Actor is on right now is recorded here too. A Store is required in order to use Spots and Actors.