Data lakehouse architecture template
Sources, ingestion, bronze/silver/gold tables on object storage, the consumers that read them, and the governance around it all.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Sources
- PostgreSQL (orders) · Salesforce + HubSpot · CSV drops from partners · Clickstream events
- Ingestion
- CDC: Debezium → Kafka · Batch ELT: Fivetran, hourly · Streaming: Spark Structured Streaming
- Lakehouse: object storage + Delta / Iceberg tables
- Bronze: raw, append-only, as ingested · Silver: cleaned, deduped, conformed · Gold: business aggregates + marts · Query engine: Spark, Databricks SQL or Trino
- Consumers
- BI dashboards (Looker) · ML features + training · Reverse ETL → CRM · Ad-hoc SQL notebooks
- Governance (across every layer)
- Catalog: Unity Catalog or AWS Glue · Column-level access control + PII masking · Lineage from source to dashboard · Data quality tests on every silver table · Retention: bronze 90 days, PII deleted on request · Time travel for audits and rollback
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
- One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.
Good for
- architect
- data lakehouse
- medallion
- data engineering
- analytics
- Agreeing on boundaries and responsibilities between services
- Recording why a design was chosen (and what was rejected)
- Comparing integration options side by side
Related templates
C4 system context diagram
C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.
C4 container diagram
C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.
Microservices with API gateway
Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.
Event-driven architecture
Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.
LLM application architecture
Production building blocks around a model: gateway, guardrails, orchestrator, cache, vector DB, tools and observability.
ML feature store
How a feature store serves the same features to training and real-time inference: batch and streaming pipelines, offline and online stores.