DuckDB 2.0 extends the embedded engine with a native networked mode

DuckDB’s planned 2.0 release keeps the single-binary model while adding a native client/server mode, remote CONNECT/ATTACH operations, and query pushdown across DuckDB, PostgreSQL, and MySQL endpoints. The preview also uses MVCC and multi-connection isolation for longer-lived, multi-tenant server deployments.

The extension story is changing just as substantially: a versioned C API with YAML-defined specification and stable ABI should stop extensions from being rebuilt for every DuckDB release, with Rust bindings planned. Teams can also pin and self-host extension repositories. General availability is targeted for the fall, so these details describe a preview rather than a finished release.