Top
Best
New

Posted by onderkalaci 18 hours ago

AWS Acquires DuckLabs(ducklabs.com)
1024 points | 300 commentspage 4
hckshr 17 hours ago|
DuckLabs does services and support around DuckDB.

"We also worried that scaling DuckLabs into a much larger sales, support, and operations organization would pull our attention away from the technical work and open-source community that made DuckDB successful in the first place."

Given AWS's services arm seems like a good play for a team. Congrats!

kimseungyong 4 hours ago||
Who is better? AWS? Google? MS?
Bluestein 18 hours ago||
Extend, embrace, quack.-
srameshc 15 hours ago||
I am happy for the team's success but I am sad and anxious for what may become of the DuckDB. It is my favorite tool. Like other comments mentioned, DuckDB is open source and MIT license so I hope it will survive and evolve further the way it did.
ganeshsivakumar 13 hours ago||
What if AWS eventually steer away duckdb team's bandwidth towards their AWS products or influence their work, since they are technically AWS employees.
sakesun 7 hours ago||
AWS name is really negative.

I trust the person leading DuckDB, nevertheless.

g8oz 4 hours ago||
I fear this is the end of the rapid pace of innovation that we've seen from DuckDb.

"AWS has committed to supporting the continued development of DuckDB and its wider community for the long term."

Those are just words man.

tosh 18 hours ago||
did not expect that

I hope the future for DuckDB is still bright

data-ottawa 17 hours ago|
Also did not expect this. I did expect MotherDuck to acquire them at some point (in fact, I kinda thought they already did!)
Fervicus 13 hours ago||
People using DuckDB, what's your use case? I use sqlite for a lot of my personal projects. What's a good use case for using DuckDB?
phainopepla2 13 hours ago|
DuckDB is for analytics, so OLAP instead of OLTP. If you're using the DB for normal transactions, stick with sqlite
Fervicus 10 hours ago||
Thanks, I gathered that much. I am curious what kind of stuff people are using it for, especially in their personal projects.
domper 3 hours ago||
One great use case I've found:

You can find monthly archives of every reddit comment on Academic torrents. These are huge NDJSON files compressed to .zst, named like 'RC_2026-01.zst'. The size is ~60GB compressed, 350GB+ uncompressed, per month.

Most of the size is taken by the actual comment text. But I was only interested in calculating how many unique commenters subreddits have in a month so I only wanted to extract a few fields from it and discard the rest.

If you use traditional tools like pandas or load the data to a database and then query it, you would quickly run out of RAM or storage space, especially when doing it on a basic laptop like I was. But with DuckDB it's just this:

``` SELECT lower(subreddit) AS subreddit, author FROM read_json(['RC_2026-01.zst', 'RC_2026-02.zst']) ```

DuckDB automatically handles decompression on the fly, figures out the schema, manages RAM so you won't OOM and so on. And even on my laptop that query takes like, 2 minutes? Which is super impressive to me.

pantsforbirds 17 hours ago|
I'm hoping this means we get an rds + s3 implementation of ducklake from AWS: https://ducklake.select/
More comments...