Live data from Hacker News

A Preview of DuckDB v2.0

duckdb.org

11–20 of 144 posts

Re: A Preview of DuckDB v2.0

#11
post #8

DuckDB is one of the things I've been most excited about in a long time. Introduced it to projects at 3 companies since 2023, greatly lowering resource requirements and running it in a variety of environments. Just having the ability to do out of core bigger than memory data processing on lower end consumer grade hardware is remarkable. Thanks to the team for everything!

Curious to learn more about how people are using it? Are they downloading parquet files and running analyses locally, or are they connecting to Iceberg-like data lake and leveraging DuckDBs query engine capabilities or have you exposed an interface (REST, UI) to query your data?

We use DuckDB WASM with parquet to build dashboards in-browser. It's cool to be able to write SQL directly in a browser and not have to rely on REST/Graphql/etc to access the data layer.

Re: A Preview of DuckDB v2.0

#12

The last year of DuckDB enhancements feel like the shift from in-process execution engine (which it is phenomenal at) to an engine that can serve as the foundation of a cloud data warehouse. I know the founders were reticent about not wanting to build that, but I have a feeling it is in the works.

UPDATE: Removed uninformed comment about the relationship between DuckDB and MotherDuck.

Wait, what? I‘ve always assumed MotherDuck is the company by the main developers of DuckDB? They are unrelated?

Re: A Preview of DuckDB v2.0

#13
post #8

DuckDB is one of the things I've been most excited about in a long time. Introduced it to projects at 3 companies since 2023, greatly lowering resource requirements and running it in a variety of environments. Just having the ability to do out of core bigger than memory data processing on lower end consumer grade hardware is remarkable. Thanks to the team for everything!

Curious to learn more about how people are using it? Are they downloading parquet files and running analyses locally, or are they connecting to Iceberg-like data lake and leveraging DuckDBs query engine capabilities or have you exposed an interface (REST, UI) to query your data?

We use WASM DuckDB as the target for an in-browser agentic feature. Generated SQL runs against the user's individual tables that then feed in-browser dashboards.

Excellent performance.

Re: A Preview of DuckDB v2.0

#14
post #7

This is cool What about the runtime size? I care this because I intend to run a stripped WASM version of DuckDB in browser.

What do you plan on stripping and what's your target? The Emscripten based build is ~10Mb. I have a component build so I'd be interesting on how you'd like to break it up.

Re: A Preview of DuckDB v2.0

#16
post #12

Earlier quoted context omitted.

UPDATE: Removed uninformed comment about the relationship between DuckDB and MotherDuck.

Wait, what? I‘ve always assumed MotherDuck is the company by the main developers of DuckDB? They are unrelated?

I was wrong. Apologies.

> They decided to work together, and DuckLabs would become a co-founder of the new endeavor.

https://motherduck.com/about-us/

Re: A Preview of DuckDB v2.0

#17

Earlier quoted context omitted.

Curious to learn more about how people are using it? Are they downloading parquet files and running analyses locally, or are they connecting to Iceberg-like data lake and leveraging DuckDBs query engine capabilities or have you exposed an interface (REST, UI) to query your data?

We use WASM DuckDB as the target for an in-browser agentic feature. Generated SQL runs against the user's individual tables that then feed in-browser dashboards. Excellent performance.

[flagged]

Re: A Preview of DuckDB v2.0

#20
post #8

DuckDB is one of the things I've been most excited about in a long time. Introduced it to projects at 3 companies since 2023, greatly lowering resource requirements and running it in a variety of environments. Just having the ability to do out of core bigger than memory data processing on lower end consumer grade hardware is remarkable. Thanks to the team for everything!

My favourite is AWS Athena (backed by Trino).

"If we use this we get indefinite RAM indefinite CPU and do not need to host a server".

I had an impression that DuckDB was not great at distributing work to other machines, but good at doing it locally? Am I wrong?

Post reply on HN