Movement — how data flows between systems

Database Connectivity

5 open standards for Database Connectivity in a modern data architecture, each with an opinionated judgement: Adopt, Situational, Assess, or Caution.

Start with JDBC, ODBC and ADBC.

Adopt 3 standards

The standard to reach for in new work. Proven, multi-vendor, clearly the default for its slot.

  • JDBC — Java Database Connectivity

    Every JVM data tool speaks it; default for 25 years.

    Java Community Process (JCP)

  • ODBC — Open Database Connectivity

    Cross-language equivalent of JDBC; sits behind every BI tool.

    ISO/IEC 9075-3 (originally Microsoft / SQL Access Group)

  • ADBC — Arrow Database Connectivity

    Arrow-native DB connectivity; the modern replacement for JDBC/ODBC on analytical workloads.

    Apache Software Foundation (Arrow project)

Assess 1 standard

Promising but not yet proven for production-default use. Track it and prototype, but don't commit your architecture.

  • Quack

    DuckDB's new client-server protocol; promising but early — watch adoption beyond the DuckDB ecosystem.

    DuckDB Labs (vendor-driven open source)

Caution 1 standard

We'd avoid it for new work — superseded or fading, but still encountered in existing systems.

  • XMLA — XML for Analysis

    Legacy SOAP-based BI protocol; survives only inside MS Analysis Services.

    XMLA Council (Microsoft, Hyperion, SAS); de-facto industry spec

More in Movement

Movement covers how data flows between systems.

See Database Connectivity in context

These standards are one panel of the interactive Data Landscape, which maps every open standard a modern data architecture is built on. The underlying data is a single JSON file; disagree with a judgement? Open an issue.