Home / Figures / Chapter 13

Figure 13.4: Many loops, one shared store

Many loops, one shared store.
Figure 13.4 Many loops, one shared store. Each loop runs on its own trigger and writes what it learns to a single on-disk store of typed signals, per-loop contracts, and one global log—never to another loop directly. A finding the support loop records (in accent) is simply standing there when the content loop next wakes and reads it, so the store does the coordinating that no loop has to. The same property makes a wrong finding travel just as far.