I'm glad that DuckDB has a foundation in place and hope it is resilient enough to push the DB forward when the time comes.
Out of all the big orgs, Amazon is probably the one that has the least regard for keeping technically interesting projects alive, and the certainly will bulldoze it for some dumb reason when the next re-org comes.
AFAIK Google is much better at not tearing well-working teams apart in reorgs, and letting people go they have acquihired a few quarters earlier.
Of the few examples I have I my head, I'd even say that the fate of a product that has been acquired by Google is probably even better than those of Google's internally developed products. e.g. Waze is still alive and kicking 13 years after acquisition under its own brand and hasn't been completely swallowed by Google Maps. The Nest brand also stuck around for quite some time.
I wasn't expecting this, and I am pleasantly surprised. I think AWS has been a bad player in the data space and very much behind all the other warehouse providers for many years now. This could lead into interesting integrations of DuckDB on top of all the data that lives in S3 and provide a leaner, faster and a more modern alternative to Athena.
Seems like a good time to recommend Apache Datafusion. It's designed to be a library, but works pretty well standalone as well. There's a CLI version, but also Python and Java bindings, as well as a Rust library, of course.
From my own experience I can say it integrates far better into your Rust app than DuckDB does.
I've been eyeballing DuckDB and LanceDB as part of AI agent memories.
This gives me a vibe that AWS will use DuckDB somehow in their ai agents sometime in the near future after seeing the potential.
Wow congratulations for the original authors, but I hope it doesn't impact the users. I can imagine that it is very useful for AWS because they don't exactly have something similar.
I use DuckDB extensively for local dev as well as a parquet viewer.
Devs gotta eat. Yeah the code is out there but the code is a result of a lot of thinking, prioritization, research into what is needed from the actual product. So now AWS owns that mindshare and talent and will (probably heavily) influence its decisions. I just hope DuckDB doesn't stray from its goal of being the SQLite (e.g. embedded) OLAP.
Out of all the big orgs, Amazon is probably the one that has the least regard for keeping technically interesting projects alive, and the certainly will bulldoze it for some dumb reason when the next re-org comes.
Of the few examples I have I my head, I'd even say that the fate of a product that has been acquired by Google is probably even better than those of Google's internally developed products. e.g. Waze is still alive and kicking 13 years after acquisition under its own brand and hasn't been completely swallowed by Google Maps. The Nest brand also stuck around for quite some time.
From my own experience I can say it integrates far better into your Rust app than DuckDB does.
Well over 100 monthly contributors, too.
And DuckLabs is the engineering behind DuckDB.
If I'm correct, this seems like a signal that AWS is coming after the segment of customers wanting to host DuckDB (MotherDucks customers).
Correct me if I'm wrong though, please.
I've been eyeballing DuckDB and LanceDB as part of AI agent memories. This gives me a vibe that AWS will use DuckDB somehow in their ai agents sometime in the near future after seeing the potential.
I use DuckDB extensively for local dev as well as a parquet viewer.
I hope the future for DuckDB is still bright
learn about it here: https://query.farm/haybarn/
https://query.farm/haybarn/
Or
https://github.com/Query-farm-haybarn
I've been releasing the versions all the way since 1.5.3 and all community extensions.