May 12, 2026
Duck, duck… DRAMA
Quack: The DuckDB Client-Server Protocol
DuckDB Finally Goes Shared—and the Crowd Is Split Between Hype, Confusion, and HTTP Rage
TLDR: DuckDB added Quack, a new way for multiple apps or people to share one DuckDB database at the same time. Commenters are torn between excitement for simple team use, confusion over DuckDB’s identity, and a heated fight over whether HTTP is smart or a future headache.
DuckDB just pulled a plot twist: the famously runs-inside-your-app database is now learning how to act more like a shared service. Its new remote system, Quack, lets multiple people and programs talk to the same DuckDB setup at once, including writing to it at the same time. For fans who’ve wanted DuckDB to move beyond the “great for one laptop, awkward for a team” phase, this is a big deal.
But the real show was in the comments, where the community immediately split into camps. One of the loudest vibes was pure identity crisis: what is DuckDB supposed to be now? One commenter basically summed up the confusion with a shrug, saying they like DuckDB but can’t always tell which of its many use cases is the “right” one. That’s classic tech launch energy: half applause, half existential crisis.
Then came the practical crowd. Some people were instantly sold on the idea for small shared analytics, team servers, and even nerdy home-lab experiments. Others zoomed straight into niche dreams, like using Quack in a DuckLake setup, proving once again that database fans can turn even the most specific feature request into a main-character moment.
And yes, there was drama. A spicy commenter flat-out rejected DuckDB’s claim that building on HTTP in 2026 is obvious, arguing it’s bad for big transfers and streaming. Translation for normal humans: one side says Quack is refreshingly simple; the other says the plumbing could become the whole problem. Bonus cliffhanger: someone immediately asked if it works in the browser with duckdb-wasm—because no launch is complete without the internet demanding one more platform.
Key Points
- •DuckDB introduced Quack, a remote protocol that allows DuckDB instances to communicate in a client-server setup.
- •Quack is intended to support multiple concurrent writers while remaining simple to deploy and using HTTP-based infrastructure.
- •The article contrasts Quack with DuckDB’s longstanding in-process architecture, which has been well suited to notebooks and embedded SQL use cases.
- •DuckDB says simultaneous modification of the same database file from multiple processes is difficult because important database state is kept in main memory.
- •Before Quack, users often relied on custom RPC layers, Arrow Flight SQL-based projects, MotherDuck’s protocol, or traditional client-server systems such as PostgreSQL.