DuckDB Labs announced 'Quack', an official client-server protocol for DuckDB that uses HTTP and serializes DuckDB's internal data vector blocks for efficient communication. Quack enables multiple DuckDB processes to write to the same database by routing writes through a server process, solving the single-writer limitation of embedded DuckDB. Current limitations include basic shared-token authentication, no HTTPS by default, and no user-level access control. MotherDuck, a cloud-hosted DuckDB service, welcomes the announcement and plans to support Quack as an endpoint type targeting DuckDB 2.0. The post also outlines where MotherDuck goes beyond self-hosted Quack: multi-user permissions, SSO authentication, separation of storage and compute, tiered and differential storage, hypertenancy, serverless scaling, SLAs, and a Postgres-compatible endpoint.
Sort: