duckdb now does async IO — no more waiting for the network

DuckDB ships an asynchronous I/O layer that lets it read files while it crunches numbers. Instead of one thread chugging through a 200 GB Parquet file and blocking the whole process, the query engine can be doing compute while the file system fetches the next chunk. The result: faster scans on cloud storage, and the kind of parallelism you usually need a whole orchestrator for, now inside the query engine.

This matters because DuckDB has been the quiet workhorse for data teams that wanted Postgres without the bloat or a warehouse without the bill. Async IO was the last piece holding it back — it could write fast, but reading from S3, GCS, or even local SSDs would stall the thread. Now it reads ahead, overlaps I/O with computation, and keeps the CPU fed. The practical effect is that single-node DuckDB can handle workloads that used to require a cluster.

Why this matters for us: la gente que trabaja con datos — en la oficina, en el side hustle, even en el taller — ya no necesita un data warehouse de $5,000 al mes para queries medianas. DuckDB sigue siendo gratis y ahora se mueve más rápido con lo que ya tiene.