Ingestion connects operational systems, files, events and external sources to a shared data platform through batch or streaming movement.
- Why it matters
- Every downstream promise depends on source coverage, freshness and recoverability at this first hand-off.
- Example tools
- Fivetran · Airbyte · Kafka · AWS DMS
- Common risks & tradeoffs
- Connector drift, unexpected schema changes, duplicated records and poorly planned backfills.
Storage includes cloud warehouses, object stores and open-table formats that persist structured and semi-structured data.
- Why it matters
- The storage model shapes cost, performance, interoperability and how quickly teams can put trusted data to work.
- Example tools
- Snowflake · BigQuery · Redshift · Apache Iceberg
- Common risks & tradeoffs
- Runaway spend, vendor lock-in, duplicated truth and unclear ownership between lake and warehouse.
Transformation applies tested logic, modelling conventions and business definitions to data so it can answer repeatable questions.
- Why it matters
- This is where shared metrics and dependable analytical products are made—or quietly broken.
- Example tools
- dbt · SQLMesh · Spark · Dataform
- Common risks & tradeoffs
- Metric drift, opaque lineage, untested business rules and models that nobody confidently owns.
Control layer 04
Orchestration
04 Orchestration determines when data work runs, what it depends on and how teams recover when a task fails.
- Why it matters
- Reliable coordination keeps complex pipelines understandable and prevents one small failure from becoming stale reporting.
- Example tools
- Airflow · Dagster · Prefect · Kestra
- Common risks & tradeoffs
- Brittle dependency graphs, alert fatigue, silent retries and operating complexity that grows faster than the team.
BI and analytics cover semantic models, exploration, dashboards and lightweight data applications used across the business.
- Why it matters
- This is where most people experience the data platform and decide whether they trust it.
- Example tools
- Power BI · Sigma · Tableau · Looker
- Common risks & tradeoffs
- Dashboard sprawl, inconsistent metrics, slow feedback loops and polished outputs with weak foundations.
AI and machine-learning layers use enterprise context to train, retrieve, reason and automate work under defined controls.
- Why it matters
- AI value is constrained by the relevance, quality and governance of the context it can reach.
- Example tools
- Databricks · SageMaker · Vertex AI · Azure AI
- Common risks & tradeoffs
- Weak evaluation, ungrounded answers, sensitive-data exposure and automation without meaningful review gates.
Control layer 07
Governance
07 Governance connects policy to daily practice through catalogues, access controls, stewardship and consistent definitions.
- Why it matters
- It lets teams move faster with confidence instead of discovering risk only after data has spread.
- Example tools
- Collibra · Alation · Microsoft Purview · OpenMetadata
- Common risks & tradeoffs
- Policy theatre, stale catalogues, unclear accountability and controls that block work without reducing risk.
Control layer 08
Observability
08 Observability monitors freshness, volume, schema, lineage and quality so teams can identify and explain incidents quickly.
- Why it matters
- Trust depends on finding problems before decision-makers do—and having enough context to fix them.
- Example tools
- Monte Carlo · Soda · Bigeye · OpenSearch
- Common risks & tradeoffs
- Noisy alerts, shallow coverage, missing business context and monitoring signals without clear response ownership.