DuckLake
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
0warn against
May 12, 2026first mention
Oct 27, 2026latest mention
Why people recommend it
“Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.”
“it's just a (good) data lake spec that works in duckdb.”
Show 1 more
“we've adopted/extended it and ducklake very heavily at Krea for our research.”
works at Kreaon “AWS Acquires DuckLabs”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Who recommends it in their own words
Threads where it came up
- DuckDB Ducklake 2 mentions
- Ask HN: How do you handle time-series metrics at scale without a large bill? 1 mention
- AWS Acquires DuckLabs 1 mention
- Quack: The DuckDB Client-Server Protocol 1 mention
Also written as Ducklake. Data: ducklake.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 5
We’re on azure and a surprisingly good choice has been to use their eventhub to ingest the telemtry and then to consume it in batches of a few seconds using a consumer. Time series is hard because it is a lot of data that comes in all the time, this allows you to relax those requirements a bit. After eventhub we’re using ducklake. But I’m not at the point where I’d flat out advise it to other people (just code immatu
“Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.”
“it's just a (good) data lake spec that works in duckdb.”
“we've adopted/extended it and ducklake very heavily at Krea for our research.”
“Our lakehouse uses ducklake with postgres as the catalog.”