DuckDB Extensions
summary
Extension system lets DuckDB stay tiny while adding features as separate modules: extensions install and load as shared libraries, CI builds platform-specific binaries and uploads them to S3-distributed binaries, and clients can install from S3 at runtime. The demo builds a real extension (byte-size formatter), runs unit and SQL tests, creates a release, and CI produces multi-arch artifacts that install from custom endpoints — the extension builds, tests, and deploys successfully within minutes.
AI-written summary · about
chapters (8)
- 0:00DuckDB extensions intro
- 1:23Why DuckDB uses extensions
- 3:13How extensions work
- 4:59Extending DuckDB
- 7:08Build extension from scratch
- 10:02Live extension demo
- 14:17Key takeaways and future
- 17:13Q&A
related talks
27mDuckDB Extensions: The Past, the Present, and the Future
39mDuckDB Extension Development Workshop – Part 1
28mState of the Duck
33mDuckDB – Overview and latest developments
05mAnnouncing DuckDB Support for Delta Lake and a DuckDB Extension to Unity Catalog
23mState of the Duck
52mThe trouble with extensions
28mAnalyze data easily with duckdb - and the implications on data architectures