DuckDB 2.0 adds a server to a database built to run without one

DuckDB co-creators Hannes Muehleisen and Mark Raasveldt add remote connections and asynchronous I/O to the LTS release, months after DuckLabs joined AWS.

By · Published

Primary source: DuckDB

Why it matters

DuckDB 2.0 expands the founders' embedded-database thesis into remote and shared use, while its storage-format change makes careful migration testing part of the upgrade.

DuckDB 2.0 takes its embedded database into client-server use — Co-creators Hannes Muehleisen and Mark Raasveldt add remote connections and asynchronous I/O to the LTS release, months after DuckLabs joined AWS.

DuckDB co-creators Hannes Muehleisen and Mark Raasveldt released DuckDB 2.0.0 on October 21st, adding client-server connections to an analytical database built to run inside an application rather than behind a separate server. The LTS release announcement introduces a more polished Quack protocol, a 'CONNECT' statement for remote databases, asynchronous I/O and other features DuckDB says reflect close to 20,000 commits since version 1.5.…

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

Reader comments

Conversation for this story loads after sign-in.