DuckDB Extensions: The Past, the Present, and the Future
summary
DuckDB extensions power real features: there are 32 core and 145 community extensions, with core extensions pulled about 27M downloads/week and community about 500k/week. Extensions auto-install via autoload installs extensions, use C++, Rust (experimental) or C templates, and ship things like Parquet, JSON, ICU and Duck Lake (open lakehouse). The current pain is an unstable C++ API that forces rebuilds; the roadmap moves toward a stable C extension API and migrating many extensions to it.
AI-written summary · about
chapters (11)
- 0:00Introduction to extensions
- 1:23Speaker background
- 2:55What are extensions?
- 4:05Why use extensions?
- 6:09Using and getting extensions
- 7:39History of extensions
- 11:22Current state and adoption
- 12:21Building and maintaining
- 14:02Future challenges and APIs
- 16:37Roadmap and takeaways
- 18:03Q&A session
related talks
18mDuckDB Extensions
33mDuckDB – Overview and latest developments
28mState of the Duck
23mState of the Duck
05mAnnouncing DuckDB Support for Delta Lake and a DuckDB Extension to Unity Catalog
27mState of the Duck
52mThe trouble with extensions
38mFrom Big Data to DuckDB: Ryan Boyd (MotherDuck) on Hyper-Tenancy, Duck Lake, and Making Data Fun.