Podorbit
DiscoverPodcastsGuestsCompanies
Podorbit

Tech podcasts · indexed by guest & company

PrivacyTermsSupport
support@podorbit.app

Guillermo Sanchez Dionis

Software Engineer

DuckDB LabsDuckDB LabsDuckLabsDuckLabs

Appearances (2)

The New Stack Podcast/Nov 14, 2026/24m

DuckDB has an answer to “bloated” database messages

DuckDB is rethinking how databases communicate with the launch of Quack 1.0, a production-ready, HTTP-based client/server protocol designed for faster, more efficient analytical workloads. In this episode of The New Stack Podcast, Guillermo Sánchez Dionis, product lead at DuckLabs, explains how Quack addresses the limitations of traditional database protocols, which often introduce unnecessary overhead and inefficient data serialization. Unlike conventional protocols built around row-based data transmission, Quack leverages DuckDB’s columnar data representation and vectorized execution engine to deliver faster, more efficient query results. Its streaming architecture allows clients to consume results as they are generated, significantly reducing memory usage and eliminating unnecessary processing delays. Sánchez Dionis also highlights developer-friendly capabilities, including simplified remote connections, command-line server deployment, and improved transaction throughput and concurrency. With minimal server overhead and the flexibility to scale across multiple DuckDB instances, Quack makes distributed analytics more accessible. The conversation explores how DuckLabs is advancing database connectivity while prioritizing performance, simplicity, and server-side stability in future releases. Learn more from The New Stack around the latest developments around DuckDB: Why MotherDuck refuses to fork DuckDB DuckDB: Query Processing Is King Join our community of newsletter subscribers to stay on top of the news and at the top of your game.

Guillermo Sanchez Dionis

Software Engineer

DuckDB LabsDuckDB LabsDuckLabsDuckLabs
Talk Python To Me/Sep 10, 2026/1h 11m

#562: DuckLake: The Lakehouse That's Just SQL and Parquet

How many files does your query read before it reads any data? On some data lakes, you go through JSON and metadata files first, just to learn which Parquet files matter. DuckLake asks one SQL question instead. The metadata lives in a real database. The data stays in plain Parquet. That's the entire format. Pedro Holanda joined DuckDB in 2018, when it was still a research prototype at CWI. He's the lead DuckLake developer. Guillermo Sanchez Dionis works on DuckLake and the new Quack protocol. With Quack as the catalog, DuckLake handles 200 transactions a second under heavy contention. No other open table format comes close. Episode sponsors Six Feet Up Talk Python Courses Links from the show Guests Pedro Holanda: pedroholanda.org Guillermo Sanchez: linkedin.com PhD on progressive indexes: ir.cwi.nl SQLite: www.sqlite.org Litestream: litestream.io boring hardware: talkpython.fm DuckDB: duckdb.org episode 491: talkpython.fm Iceberg: iceberg.apache.org manifesto: ducklake.select DuckLake: ducklake.select spec: ducklake.select this diagram: blobs.talkpython.fm Data inlining: ducklake.select ducklake-dataframe: github.com Polars course: training.talkpython.fm CSV parser: duckdb.org Zero-copy Arrow: duckdb.org ART index: duckdb.org async I/O: duckdb.org v1.0: ducklake.select Git-like branching: ducklake.select Watch this episode on YouTube: youtube.com Episode #562 deep-dive: talkpython.fm/562 Episode transcripts: talkpython.fm Theme Song: Developer Rap 🥁 Served in a Flask 🎸: talkpython.fm/flasksong ---== Don't be a stranger ==--- YouTube: youtube.com/@talkpython Bluesky: @talkpython.fm Mastodon: @talkpython@fosstodon.org X.com: @talkpython Michael on Bluesky: @mkennedy.codes Michael on Mastodon: @mkennedy@fosstodon.org Michael on X.com: @mkennedy

Pedro Holanda

Lead DuckLake Developer

DuckDB LabsDuckDB LabsDuckLakeDuckLake
Guillermo Sanchez Dionis

Software Engineer

DuckDB LabsDuckDB LabsDuckLabsDuckLabs