DuckDB Introduces Quack: A Client-Server Protocol for Remote Database Communication
By
The DuckDB team
19d ago· 17 min readenNews
96/100
Golden Brown
Bagelometer↗
Kettled twice. Extra chewy, extra trustworthy.
Score96TypenewsSentimentpositive
Summary
DuckDB has introduced the Quack remote protocol, enabling DuckDB instances to communicate in a client-server architecture with support for multiple concurrent writers. The protocol is built on HTTP, is simple to set up, and is designed to handle workloads ranging from bulk operations to small transactions efficiently.
Key quotes
· 4 pulledDuckDB instances can now talk to each other using the Quack remote protocol.
This lets you run DuckDB in a client-server setup with multiple concurrent writers.
In DuckDB's spirit, Quack is simple to set up and builds on proven technologies such as HTTP.
It's also fast, which allows it to support workloads ranging from bulk operations to small transactions.
DuckDB instances can now talk to each other using the Quack remote protocol. This lets you run DuckDB in a client-server setup with multiple concurrent writers. In DuckDB's spirit, Quack is simple to set up and builds on proven technologies such as HTTP.
