DuckDB launches Quack protocol, turning the embedded DB into a multi-client server database
KhuyenTran16 · x · 2026-09-03
DuckDB has released the Quack protocol (beta), letting DuckDB processes talk over the network and turning the embedded analytics engine into a general-purpose client-server database. Key points:
- Servers start with CALL quackserve() (default port 9494) with token auth; clients connect via the Quack extension
- Full DuckDB feature set, optimized for fewer round trips and both small updates and large batches
- Storage backends span DuckDB files, DuckLake (object storage + Parquet with snapshots/time travel) and flat files, keeping ACID transactions, primary keys and indexes
- Unveiled by founder Hannes Mühleisen at AI Council 2026; setup takes minutes
Related event: DuckDB launches Quack to enable multi-client shared analytics(2 posts)→
More from coding & agent
- Agentic market-making token BUN hits 1,185 holders in 16 hours with no bundled supply — 0xSammy · 2026-09-03
- You don't need Python to learn agents: start from organizational theory, says KarlMuth — KarlMuth · 2026-09-03
- Stop letting Claude burn your subscription: a 10x token-saving workflow — alexcovo_eth · 2026-09-03
- Reply to Andrew Ng: flexibility beats rigidity in agent workflow design — KarlMuth · 2026-09-03
- Ng's four agent principles still hold; researcher suggests beginners start with a jury design — KarlMuth · 2026-09-03
- Automation vs Fixed Agent vs Malleable Agent: A Simple Framework — dfinke · 2026-09-03