← Library

Part 5 · Tools of the trade · 1 of 6

The Modern Data Stack: a Map

Where each category of tool sits between a source system and a decision, which vendors lead each category, and which pieces of Meridian's stack they correspond to.

2 min read

Vendors change; the layers don't. Read the stack left to right, the way data flows, and every tool name becomes a position rather than a brand.

LayerWhat it doesTypical toolsAt Meridian
SourcesOperational systems that create dataCRM (Salesforce, HubSpot), ERP (SAP, NetSuite), product events, filesThe CRM, the billing system
Ingestion / integrationMove data from sources into storage; batch or streamingFivetran, Airbyte, Informatica, Talend, Ab Initio, Kafka, Kinesiscrm_deals_ingest, transactions_ingest
Storage + computeWarehouse or lakehouse where data lands and SQL runsSnowflake, Databricks, BigQuery, Redshift, Microsoft FabricThe database behind the labs (SQLite stands in)
Transformation + orchestrationTurn raw tables into modelled, tested tables on a scheduledbt, Spark, Airflow, Dagster, Prefectgold_sales_metrics and its daily run
Semantic layer + BIDefine metrics once; explore and visualiseLooker, Tableau, Power BI, Qlik, Metabase, RedashThe Sales Funnel Accelerator dashboard
Quality, observability, catalog, governanceKnow it's fresh, complete, unique; find it; control accessMonte Carlo, Great Expectations, Soda, Collibra, Alation, Atlan, Unity Catalog, DataOSThe week 3 SLOs, the ontology in week 6
ML / data scienceTrain, track, and serve modelsMLflow, SageMaker, Vertex AI, Dataiku, JupyterThe agent pilot in week 6

Three things a Data PM keeps straight

  1. ETL vs. ELT. Classic tools (Informatica, Ab Initio) transform before loading into a warehouse. The modern pattern loads raw data first (Fivetran) and transforms inside the warehouse (dbt): ELT. That's why Bronze/Silver/Gold exists.
  2. Batch vs. streaming. A nightly load is batch (Airflow-scheduled). Events arriving continuously are streaming (Kafka, Kinesis). Most sales analytics is batch; fraud and operations are streaming.
  3. Where the definition lives. If "revenue" is computed in five dashboards, you have five definitions. Semantic layers (Looker's LookML, dbt's metrics, DataOS contracts) exist to define it once, in one place, and have every consumer read it.

How to read Gartner's market categories

Gartner splits this into Cloud Database Management Systems (warehouses and lakehouses), Data Integration Tools, Analytics and BI Platforms, Data Quality Solutions, Metadata Management / Data Catalogs, and Data Science and ML Platforms. The categories map one-to-one onto the rows above. When someone says "we're evaluating a Magic Quadrant leader," ask which row.

Source: Synthesized for DPM Lab; category structure follows Gartner's data & analytics markets.

Where this shows up