Goal: data platform
Reader: Data engineers describing pipelines, storage, models and schemas. Meta cluster: C — infrastructure & governance Scenarios: 3 · Examples: 3
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| entity relationships | T2 | plantuml | entity-relationships-crows-foot.md |
| lakehouse architecture | T2 | plantuml | data-platform-lakehouse.md |
| ml pipeline | T2 | plantuml | machine-learning-pipeline.md |
Reading order
Pipeline shape (ingest → transform → serve) first, schema second, model training loops third.
Engines in this goal
plantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- Drawing storage as a plain box when it is a warehouse/lake distinction
- Omitting the freshness or ownership of each stage