Architecture in practice
Multi-region service
Compare two regional paths. This is a design example, not a Flowboard residency promise.

Start from template Download JSON
This opens a separate browser draft; your main draft remains unchanged.
Readable source
The labels explain the system to a reader. Stable identifiers connect the nodes to the flows. Keep a copy of this source, then adjust it to match your own architecture.
# Multi-region service
- Traffic router {#router type=service detail="Routes requests" x=80 y=230}
- Region A API {#a type=service detail="Serves region A" x=410 y=100}
- Region B API {#b type=service detail="Serves region B" x=410 y=390}
- Region A data {#da type=database detail="Stores region A records" x=740 y=100}
- Region B data {#db type=database detail="Stores region B records" x=740 y=390}
## Flows
- router -> a {#primary label="primary path"}
- router -> b {#secondary label="secondary path"}
- a -> da {#read-a label="local data"}
- b -> db {#read-b label="local data"}
Make one useful change.
Rename a component, explain a connection or add a note about a missing assumption. Export the result as Markdown, JSON or YAML to keep an editable copy.
Learn the import and export workflow