Architecture in practice
API and database
Rename one service and trace a request to its persistent store.

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.
# API and database
- Customer {#client type=client kind=person detail="Uses the application" x=80 y=100}
- API {#api type=service kind=software-system detail="Handles requests" x=400 y=100}
- Database {#db type=database kind=data-store detail="Stores records" x=720 y=100}
## Flows
- client -> api {#request label="Uses" protocol="HTTPS"}
- api -> db {#query label="Reads and writes records" protocol="SQL"}
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