I'm relatively new to DuckDB (coming from SQLite) and I love it so far. Some parts are magical (described in the previous article by the same author: <a href="https://peterdohertys.website/blog-posts/dab-of-duck.html" rel="nofollow">https://peterdohertys.website/blog-posts/dab-of-duck.html</a>)<p>You can point DuckDB to almost any data source and boom, you get an SQL table that you can search, sum, or join to any other data. Or you can attach existing databases from completely independent db systems, and query and join them as one, without having to first importing anything.<p>It feels exhilarating (if you're into that sort of thing!)
We wrapped exactly this into a GUI - attach MySQL and PostgreSQL, files/ s3 as sources, query them together with DuckDB. No imports.
<a href="https://streams.dbconvert.com/cross-database-sql" rel="nofollow">https://streams.dbconvert.com/cross-database-sql</a>
My honeymoon with duckdb wore off pretty quickly when I need to compile it, myself, into a single-file concordance. I understand it's open source, so I'm free to be ignored. But, it's positioning itself as a drop-in replacement for SQLite; a large part of SQLite's appeal is its ergonomics — its single-fileness — letting me deliver a rational object to my users.