3 ms·
I was a real fan from the very beginning, but now DuckDB 2.0 "as a server" and 5. asynchronous I/O [1] looks aimed at something very different from what I thoug
by janpeuker 1mo ago
I was a real fan from the very beginning, but now DuckDB 2.0 "as a server" and 5. asynchronous I/O [1] looks aimed at something very different from what I thought first.
1) https://duckdb.org/2026/08/17/duckdb-20-highlights https://duckdb.org/2026/08/17/duckdb-20-highlights
- tuvix 1mo agoAgreed that DuckDB as a server feels far from their initial mission, but how does async IO divert from it?
- janpeuker 1mo agoI didn't even necessarily mean diverting from the mission, just that optimising for network storage now reads like a feature maybe prioritised in anticipation of a stronger cloud user base
- skeeter2020 1mo agoagree - I was really uneasy with the lede in their v2.0 preview: "DuckDB has been an in-process database since day one. But people have asked us – very persistently – for a client/server mode, and we have finally caved" This was already satisfied by numerous projects and products, and feels like a "me too" attempt to capture AI-based workflows. DuckDB always felt like "SQLite for Analytic Data" but I fear these changes and now acquiring the org leading technical direction is where they deviate for good. AWS is so unnecessary for what DuckDB can (and should, IMO) be; MongoDB jumps to mind as a cautionary tale.