Analyze data easily with duckdb - and the implications on data architectures
summary
DuckDB is an in-process analytical engine that queries Parquet/JSON over HTTP and S3 (example: reads a 2.5 GB JSON blob) and can attach tiny catalog files (few KB) that point to distributed sources. It interoperates with Python via Pandas/Polars/Apache Arrow with near-zero conversion cost and runs in the browser via WASM execution. Teams replace slow PySpark unit tests and some ETL jobs (claims of hours→minutes) and run DuckDB in Lambda; limitations remain: single-node, limited multi-user and write support for some lakehouse formats. Version 1.3 targets Iceberg/Delta performance.
AI-written summary · about
chapters (11)
- 0:00Introduction to DuckDB
- 1:02Demonstrating core features
- 7:03Managing persistent databases
- 8:33Python and ecosystem integration
- 11:29Web and browser capabilities
- 12:52Conceptual architecture
- 14:15Flexibility and extensions
- 17:00Practical use cases
- 18:56Benefits and limitations
- 22:15Impact on data architecture
- 24:16Conclusion and Q&A
related talks
27mIn Process Analytical Data Management with DuckDB
34mData Wrangling with DuckDB
01h 02mAnalytics for not-so-big data with DuckDB
40mDuckDB: Harnessing in-process analytics for data science and beyond
40mDuckDB beyond the notebook
27mThe Duck and the DataFrame: A Data Engineer’s Journey with DuckDB
25mA quack of all trades: DuckDB, a versatile analytical database to keep in your toolkit
19mIn-Process Analytical Data Management with DuckDB
