DuckDB announced Quack, the DuckDB Client-Server Protocol, on May 12, 2026, marking a major architectural expansion for the popular analytical database. The protocol enables multiple concurrent writers to modify database tables in parallel without lock conflicts, transforming DuckDB from a strictly in-process database into a distributed system while maintaining its signature simplicity.
Quack Enables True Multi-Writer Concurrent Access
The Quack protocol allows DuckDB instances to communicate using a remote protocol that supports multiple separate processes—locally or remotely—modifying table contents simultaneously. This "multiplayer experience" eliminates the write-locking constraints that previously limited DuckDB to single-writer scenarios. DuckDB instances can now function as both client and server, whether running on different computers across the globe or in separate terminal windows on the same laptop.
Built on HTTP for Simplicity and Performance
Quack is built directly on HTTP (Hypertext Transfer Protocol), leveraging proven web infrastructure rather than creating proprietary networking layers. Designing a database protocol from scratch in 2026 allowed the DuckDB team to learn from existing protocols, including Arrow Flight SQL, without legacy constraints. The HTTP foundation delivers performance sufficient for workloads ranging from bulk operations to small transactions while keeping setup straightforward.
Available in DuckDB v1.5.2 Release
The Quack protocol is available in DuckDB v1.5.2, the current release version, and lives in the core_nightly repository. Setup remains simple in DuckDB's characteristic style, requiring minimal configuration to enable client-server deployment. This accessibility aligns with DuckDB's philosophy as an embedded SQL OLAP database management system—comparable to SQLite but optimized for analytical queries—now extended with distributed capabilities.
Key Takeaways
- DuckDB's Quack protocol enables multiple concurrent writers to modify database tables in parallel without lock conflicts, announced May 12, 2026
- Built on standard HTTP rather than proprietary protocols, learning from existing systems like Arrow Flight SQL
- Available in DuckDB v1.5.2 and supports workloads from bulk operations to small transactions
- Instances can run as both client and server, locally or remotely, while maintaining DuckDB's simplicity philosophy
- Represents a major architectural shift from in-process-only to distributed deployment for the analytical database