# Quack for DuckDB

20 Hacker News commenters recommended Quack for DuckDB and 2 criticized it, November 2025 to November 2026. It was recommended in 4 of 13 months. It meets the Hacker Approved badge rule.

**Verdict:** People recommend Quack for sharing a high-memory DuckDB server and its cache across a team, and for easing DuckDB's single-writer concurrency limit.

## Why people recommend it

- Shared server and cache for teams (2 comments): "The big benefit of this server protocol is sharing a high memory server and taking advantage of a shared cache for recent data." ([source](https://news.ycombinator.com/item?id=48114435)) "Sounds useful for small-ball internal analytics datasets you want to place on shared team server." ([source](https://news.ycombinator.com/item?id=48113833))
- Eases single-writer concurrency limit (2 comments): "The single-writer limit was always the awkward part. Quack finally addresses it." ([source](https://news.ycombinator.com/item?id=49350572)) "the sharp points around concurrency are relaxing" ([source](https://news.ycombinator.com/item?id=49334320))
- Strong option for DuckLake catalogs (3 comments): "I think that Quack will become the primary option for a DuckLake catalog in the future" ([source](https://news.ycombinator.com/item?id=48114693)) "Seems like a DuckDB / Quack catalog would be an excellent alternative." ([source](https://news.ycombinator.com/item?id=48114417)) "think duckdb/ducklake/quack could potentially be a future replacement" ([source](https://news.ycombinator.com/item?id=48122846))
- Resolves problems encountered with DuckDB (2 comments): "This perfectly solves that, along with several other similar kinds of problems I've encountered with duckdb." ([source](https://news.ycombinator.com/item?id=48116922)) "Yes, Quack resolves this problem." ([source](https://news.ycombinator.com/item?id=48115018))

## Cite as

Hacker Approved, "Quack for DuckDB", https://hackerapproved.com/p/quack/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).