architectureIntermediate
Why we run DuckDB behind Parquet in the F1 pipeline
A one-file warehouse has real tradeoffs. Here's how we split writes to Parquet and kept DuckDB read-only for serving.
DuckDBParquetdbt
@marco
8 min read·3d ago
Architecture breakdowns, postmortems, debugging stories, workshop recaps.
A one-file warehouse has real tradeoffs. Here's how we split writes to Parquet and kept DuckDB read-only for serving.
A 20-minute lag spike, one flipped consumer flag, and a lesson in how partition assignment strategy is not a detail.
A story about dependency chains, VC++ runtimes, and why 'works on my machine' is a valid bug report.
From typo fix to project donation in six months. How the sandbox lowered the barrier to donating real systems.