Learn  /  What's new

The modern data stack in 2026: the trends that actually matter

Fewer tools, more open formats and AI built into the platform. What has changed, and what it means for data teams.

What's new9 min readUpdated 18 October 2026
Analytics engineeringSnowflakedbtDatabasesWhat's new
All guides and cheat sheets

A few years ago, the "modern data stack" meant assembling a dozen specialist tools. The picture in 2026 is calmer and more pragmatic: consolidation, open formats and AI features built into the platforms teams already use. Here are the trends worth understanding, and what they mean in practice.

A typical 2026 data stack
Sourcesapps, SaaS, files
IngestionFivetran, Airbyte, native
Storagewarehouse or Iceberg tables
Transformationdbt models and metrics
ConsumersBI, notebooks, AI agents

1. Open table formats go mainstream

Apache Iceberg has become the leading open table format: a way of storing tables as files in your own cloud storage while keeping warehouse features such as transactions, schema changes and time travel. Snowflake, Databricks, Google, AWS and others all support it in some form.

Why it matters: data can stay in one open format while different engines query it. That reduces lock-in and duplication, and means your choice of query engine is less permanent than it used to be.

2. Local-first analytics with DuckDB

DuckDB has become a favourite tool for analysts and engineers: an in-process analytical database that queries CSV, Parquet and Iceberg data at impressive speed on a laptop. Paired with services like MotherDuck, it also scales into the cloud.

Why it matters: many workloads that once needed a warehouse can run locally and cheaply, which is great for development, testing and small organisations. See choosing the right database.

3. Faster tooling for analytics engineering

dbt Labs introduced the dbt Fusion engine in 2025, a rewrite of dbt's engine in Rust that understands SQL rather than treating it as text. In September 2026 it became simply dbt v2, with much faster parsing, errors caught before the warehouse sees them, and column-level lineage. Fivetran and dbt Labs, which announced their merger in October 2025, completed it in June 2026, a sign of consolidation across the ingestion and transformation layers.

  1. dbt Fusion engine announced

    A Rust rewrite that understands SQL.

  2. Fivetran and dbt Labs announce a merger

  3. Merger completed

    Fivetran + dbt Labs.

  4. dbt v2 generally available

    Fusion becomes the dbt engine.

Why it matters: analytics engineering is converging with mainstream software development: fast feedback, strong tooling, and fewer separate vendors to manage.

4. Postgres moves next to the warehouse

In 2025, Snowflake acquired Crunchy Data and Databricks acquired Neon, both PostgreSQL specialists. The major data platforms now want to host the transactional databases behind applications, not just analytics.

Why it matters: the boundary between operational and analytical data is blurring. Expect simpler paths from application data to reporting, and more "data apps" built directly on the platform.

5. AI inside the data platform

Warehouses now ship AI features natively: Snowflake's Cortex AI functions, for example, let you call large language models from SQL to classify, summarise or extract information from text, and natural-language assistants let business users ask questions of governed data.

SQL
-- Illustrative: classify customer feedback with an AI SQL function in Snowflake
SELECT
    feedback_id,
    feedback_text,
    SNOWFLAKE.CORTEX.SENTIMENT(feedback_text) AS sentiment
FROM raw.customer_feedback;

In 2026 both platforms went further, with AI agents for business users and builders: see Snowflake vs Databricks for AI agents.

Why it matters: unstructured text becomes something you can model and report on with SQL. It also raises the stakes for governance: AI answers are only as good as the definitions and data quality behind them.

6. The semantic layer matters more than ever

When people, and now AI assistants, ask "what was revenue last quarter?", someone has to define "revenue" exactly once. Semantic layers and metrics definitions, such as those in dbt, Power BI models and warehouse-native semantic views, are becoming the foundation that makes self-service and AI trustworthy. More in The semantic layer is back.

What this means for teams

  1. 1

    Invest in fundamentals

    Clean models, clear definitions and tests matter more with AI, not less. Start with the star schema and data quality tests.

  2. 2

    Prefer open formats

    Where practical, to keep future options open.

  3. 3

    Consolidate tools

    Fewer, better-integrated tools are easier to govern and cheaper to run.

  4. 4

    Try AI features on governed data

    With clear definitions, before rolling them out widely.

Check your understanding

1/3What is the main benefit of an open table format such as Iceberg?

2/3Why do clear definitions matter more with AI in the platform?

3/3Which database did both Snowflake and Databricks move to host?

This month's platform news in detail: Snowflake, Databricks, Microsoft Fabric at FabCon Europe, Apache Spark 4.2 and dbt Charts.

This field moves fast. Product names, features and deals change; check vendors' official announcements for the current status before making decisions.

Alessandro Ecclesie AgazziWritten by Alessandro Ecclesie Agazzi, analytics engineer in London. Updated 30 September 2026. About me

Found this useful?

New guides and "what's new" explainers on data and AI land here regularly. Follow along on LinkedIn, or share this one with a colleague.