I built something on top of DuckDB last year but it never got deployed. They wanted to trust Postgres.

I didn't use the in browser WASM but I did expose an api endpoint that passed data exploration queries directly to the backend like a knock off of what new relic does. I also use that same endpoint for all the graphs and metrics in the UI.

DuckDB is phenomenal tech and I love to use it with data ponds instead of data lakes although it is very capable of large sets as well.

▲

whalesalad 7 days ago | parent | next [-]

Cool thing about DuckDB is it can be embedded. We have a data pipeline that produces a duckdb file and puts it on S3. The app periodically checks that assets etag and pulls it down when it changes. Most of our DB interactions use PSQL, but we have one module that leverages DuckDB and this file for reads. So it's definitely not all-or-nothing.

	▲	zenmac 7 days ago \| parent [-]
		Are you using pg_duckdb to embedded it inside postgres and access it via psql or other pg clients?

▲

victor106 6 days ago | parent | prev [-]

> data ponds instead of data lakes

What are data ponds? Never heard the term before

▲

leetrout 6 days ago | parent [-]

Haha, my term. Somewhere between a data lake and warehouse - still unstructured but not _everything_ in one place. For instance, if I have a multi-tenant app I might choose to have a duckdb setup for each customer with pre-filtered data living alongside some global unstructured data.

Maybe there's already a term that covers this but I like the imagery of the metaphor... "smaller, multiple data but same idea as the big one".

	▲	victor106 5 days ago \| parent [-]
		Got it, Thanks for the explanation.