Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Acquires DuckLabs

ducklabs.com

Post reply on HN
Print view View original

121–130 of 307 posts

Re: AWS Acquires DuckLabs

#121

Post by bushbaba »

Scubabear68 wrote: post #63
daviewales wrote: post #34

The title is misleading. AWS acquired DuckLabs, NOT DuckDB. The DuckDB source code is still owned by the nonprofit DuckDB Foundation. Quote from the article: "As the CWI representative on the DuckDB Foundation... When DuckLabs spun out of CWI, we created this foundation, which holds all IP of open-source DuckDB, and will continue to do so." - Peter Boncz

This is an important distinction, I hope the title can be changed. I was really surprised when I first came across DuckDB at how good at it is for its target use cases. It is a game changer for me for the "local analytics" space, and its ability to scale up to a large degree helps a lot. It is simply awesome to be able to point DuckDB at a mess of CSV and other files and have an instant database on top of it that I c…

It’s faster than trino and spark for 99% of your use cases. Only once the datasets reach the 100GiB to TiB range is trino/spark faster. Compute is scaling vertically faster than Data Eng/Analytics dataset growth, over time DuckDB will be the better choice.

Re: AWS Acquires DuckLabs

#123

Post by tuvix »

janpeuker wrote: post #82

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

Agreed that DuckDB as a server feels far from their initial mission, but how does async IO divert from it?

Re: AWS Acquires DuckLabs

#125

Post by janpeuker »

tuvix wrote: post #123
janpeuker wrote: post #82

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

Agreed that DuckDB as a server feels far from their initial mission, but how does async IO divert from it?

I 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

Re: AWS Acquires DuckLabs

#128

Post by dkga »

I am a big fan of the Duck team since before their v1.0 and I am happy for them personally for the big payoff, both in monetary terms but also in terms of scale and longer-term viability of their baby. I am also happy to see the arrangement will keep the core OSS. Let's see what the future holds now!

Re: AWS Acquires DuckLabs

#129

Post by MeetingsBrowser »

fwip wrote: post #104
jshen wrote: post #88

Earlier quoted context omitted.

Sure, but that's not generational wealth.

We must be operating on different definitions. Generational wealth means you have enough money to meaningfully improve the lives of your kids and give them a leg-up on life. A million dollars is enough to buy a house for each of your 2.5 kids. If getting a million dollars wouldn't affect how much money you can leave your kids, you already have generational wealth.

The commonly accepted definition of generational wealth ranges from around 1.5 to 5 million per child.
Post reply on HN