Layered System Architecture Stack

完整 Prompt

A five-layer abstraction stack diagram, drawn as a vertical stack of horizontal slabs.

Top to bottom (each slab is a labeled rectangle with rounded corners):

Layer 5 — Federation
- KGRAG-style orchestrator coordinating multiple sub-systems

Layer 4 — Application
- Domain-specific business logic and workflows

Layer 3 — Service
- API gateways, authentication, rate limiting

Layer 2 — Data
- Persistence stores (relational, vector, object) and message buses

Layer 1 — Infrastructure
- Compute, network, storage primitives

Annotations:
- Each layer has a single one-line responsibility.
- Each layer's dependency arrow points strictly downward; no upward or sideways arrows.
- A small "depends only on layers below" caption near the bottom.

Style: clean systems-architecture diagram, restrained palette (5 hues from cool to warm bottom-up), white background, sans-serif labels. Suitable for engineering blog posts and infra textbooks.

适用场景

For systems architecture explanations, infrastructure decks, and clean-architecture education.

变体

使用建议

• Use 4-6 layers. Fewer feels trivial; more becomes unscannable.
• Always show dependency direction explicitly (downward arrows). It's the defining property.
• Limit each layer label to one line. Multi-line labels destroy the clean stack rhythm.

常见问题