Loading video...

Video Failed to Load

Go Home

Web Analytics in the browser with DuckDB WASM: Filtering in milliseconds, instead of waiting for API responses

56,910 views • 1 year ago •via X (Twitter)

11 Comments

Tobias Müller's profile picture
Tobias Müller1 year ago

This demo attaches a remote DuckDB database from S3 with credentials via Cognito.

Tobias Müller's profile picture
Tobias Müller1 year ago

The project will be open sourced soon. In the meantime, you can explore the power of DuckDB in a browser with @usesqlworkbench as well:

Alvar Lagerlöf's profile picture
Alvar Lagerlöf1 year ago

@duckdb Does it hold up with 10 million events?

Matt Holden's profile picture
Matt Holden1 year ago

@duckdb Wow, looking nice! Is this still using duckdb-wasm-kit?

Tobias Müller's profile picture
Tobias Müller1 year ago

@duckdb Yes, it does! Thanks for all the your work you put in it!

Alexander Hupfer's profile picture
Alexander Hupfer1 year ago

@duckdb That’s what @fusionmetrics implemented a year ago. Works pretty well in production but we need to take care of not hitting the browser memory limit (about 2GB or so)

TArch's profile picture
TArch1 year ago

@duckdb So you are saying that dowloading a whole database is better than api call? Yeah, if you dont have users you have to issues

Tobias Müller's profile picture
Tobias Müller1 year ago

@duckdb Have you tried other tools in this space? Each API calls run database queries in the backend. I tried a lot of them, and you see latencies of hundreds of ms to even seconds. If you filter/drill-down a lot, it will definitely be better to download a few MBs once, and query locally

ryan boyd's profile picture
ryan boyd1 year ago

@duckdb love it!

🇯🇲 Marquin 🇵🇸's profile picture
🇯🇲 Marquin 🇵🇸1 year ago

@duckdb Looks like Umami analytics

Tobias Müller's profile picture
Tobias Müller1 year ago

@duckdb I think most of the tools look pretty similar because they all show the more or less same stats, but Umami is among the ones I like the most...

Related Videos