SequenceSystem architectureSimple
Client to server data flow
Sequence of calls from a web client through backend services to the database and cache.
What this diagram shows
Step 01
Cache-aside read
Service asks cache first. On miss, falls through to the database.
Step 02
Write-through
Fresh rows are written back to the cache so the next read is warm.
Step 03
Response bubble-up
Payload travels back through the gateway to the original client.
About sequence diagrams
Sequence diagrams show how participants exchange messages over time. They are a natural fit for API calls, authentication handshakes, and distributed flows where timing and order matter.
This template is written in Mermaid — plain text you can edit, version in git, and regenerate the image from any time.
View Mermaid sourcePlain-text diagram syntax — copy or edit directly.
diagram.mmd
1sequenceDiagram2 participant C as Client3 participant G as Gateway4 participant S as Service5 participant DB as Database6 participant K as Cache78 C->>G: GET /items9 G->>S: forward request10 S->>K: lookup11 K-->>S: miss12 S->>DB: query13 DB-->>S: rows14 S->>K: write-through15 S-->>G: payload16 G-->>C: 200 OKRelated
Related templates
More templates that cover similar workflows.
