Architecture in practice

API and database

Rename one service and trace a request to its persistent store.

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
- Client {#client type=service x=80 y=100}
- API {#api type=service x=400 y=100}
- Database {#db type=database x=720 y=100}
## Flows
- client -> api {#request label="HTTPS request"}
- api -> db {#query label="read and write"}

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