Can DuckDB scale ? ft. Jake Thomas, Jordan Tigani, Michael Ritchie

In this panel, ⁨@mehdio is joined by three fascinating guests, each with unique experience in scaling DuckDB: Jake Thomas from Okta, Jordan Tigani from MotherDuck, and Michael Ritchie from Definite. 📓 Resources Smallpond : https://github.com/deepseek-ai/smallpond 3FS : https://github.com/deepseek-ai/3FS Blog overview on smallpond : https://mehdio.substack.com/p/duckdb-goes-distributed-deepseeks Jake Thomas's usage of DuckDB at Okta : https://www.youtube.com/watch?v=TrmJilG4GXk Michael Ritchie's company : https://definite.app/ ➡️ Follow Us LinkedIn: https://linkedin.com/company/motherduck X/Twitter : https://twitter.com/motherduck Blog: https://motherduck.com/blog/ Community Slack : https://slack.motherduck.com/ 0:00 Intro panelist 2:04 When did you start using DuckDB ? 6:51 Why DuckDB has a single node strategy ? 9:05 The fear of scaling DuckDB 21:09 Smallpond from DeepSeek and scaling DuckDB strategies 29:02 Average data size workloads is not "big" 41:02 3FS from DeepSeek, is this for me ? 50:09 What are the trends of DuckDB #duckdb #deepseek