Older database protocols often send query results row by row, repeating details like column names and types with each row. This method creates a 'bloated message' due to significant overhead, especially when transferring large query results. This design is not optimized for modern big data analytical systems.
DuckDB's solution to this inefficiency is Quack, an HTTP-based protocol that streams query results in batches of column data as they are produced. Quack was previewed in May and officially released in October as part of DuckDB 2.0.0 LTS. This design allows developers to begin processing results even while a query is still executing.
Traditional database protocols were often designed before the era of big data, primarily for transactional systems, using serialized rows rather than columns. While some evolved to use columns, they still serialized values one at a time. Quack aims for a more efficient approach by using vectorized execution and efficient columnar data representations for data transfer.
With its production release in DuckDB 2.0.0 on October 21, Quack now offers developer-friendly features. These include the CONNECT statement, which enables developers to attach to and query a remote Quack server using standard SQL commands, and a new -serve CLI argument for instantly starting a server.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
DuckDB 2.0.0 LTS released in October includes Quack, a new HTTP-based protocol designed to improve data transfer efficiency by streaming query results in batches of column data. This addresses the overhead of older database protocols that send row-by-row results with repeated metadata, which is inefficient for large analytical queries.