Use the base skill for software architecture, cloud systems, microservice maps, and deployment views. Use the Academic Overlay when the same figure is intended for publication.
tech-blue: general light-background engineering documentationarch-dark: role-coded dark architecture and cloud diagramsblueprint: formal architecture, UML, and network topologyacademic or academic-color: publication figures through the overlaymeta:
title: Order Platform Architecture
theme: arch-dark
layout: horizontal
| Role | Node type |
|---|---|
| client or frontend | user |
| backend API or worker | service or process |
| database or persistent store | database |
| managed cloud service | cloud |
| event bus or queue | queue |
| third-party system | terminal or document |
Let the theme own role colors. Use explicit fills only when the source or product identity requires them.
Represent regions, accounts, networks, and security groups as transparent modules. Keep their labels above member nodes and leave enough headroom for the boundary title.
Use concise two-line component labels when the technology matters:
nodes:
- id: api
label: "API Server\nFastAPI :8000"
type: service
module: app
| Meaning | Edge type |
|---|---|
| primary request path | primary |
| data or asynchronous flow | data |
| authentication or optional relation | optional |
| infrastructure dependency | dependency |
Bind every connector to source and target node ids. Label protocols and ports on the edge, and run validation to catch crossings, overlaps, and label-clearance problems.