Don't think it's widely known or understood, but Ducklake doesn't require duckdb: it's just a (good) data lake spec that works in duckdb.

There's a cool alternate rust/datafusion ecosystem initiative going on at https://github.com/datafusion-contrib/datafusion-ducklake, and think the Quack protocol opens up a lot of cool possibilities too.

If you need an idea for what do do with ducklake: recommend throwing all of your agent traces in it.

It's alright, it's pretty alpha software. On v1.5.4, catalog filtered counts are broken, afaik. I went to main/v2 to fix it, and then the SQL parser in duckdb v2 is 10x slower, which was another wrench in the gears. It's been a bit of a pain tbh

Yep, they made the spec 1.0 but it isn’t 1.0 software. Browse the bugs before use.

When it works well it’s really nice. And it beats handrolling a multi level parquet store.

Motherduck is offering a free copy of O'reilly's "DuckLake: The Definitive Guide" book on their DuckLake web page

https://motherduck.com/product/ducklake/

But "Duckpond" was right there!

DuckDB is the best thing world got since 1990s.

https://duckdb.org/2025/05/19/the-lost-decade-of-small-data....

DuckDB has been around since 2018. Naturally its offspring use C++.