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

271–280 of 300 posts

Re: AWS Acquires DuckLabs

#271

Post by adsharma »

adsharma wrote: post #269

Surprised that there isn't more discussion of DuckDB source distributions. Why do we need a source distribution for a well regarded MIT licensed project? Because it's not easy to contribute code to DuckDB if you don't work at DuckLabs. The CI used to take 5 hours for a simple bug fix last I looked (may have improved since I flagged it on social media). There are two that I'm aware of: * Haybarn: https://rusty.today/b…

Several "Graph on DuckDB" efforts started on DuckDB and ended up reinventing a basic columnar codebase to innovate on because of these reasons. Even though people didn't document why, lack of outside contributor friendly flows is likely one of the reasons.

KuzuDB folks worked on something called GRainDB in 2022: https://vldb.org/cidrdb/2022/graindb-a-relational-core-graph...

But circa 2023 decided to write their own. Work continues as LadybugDB. One of my long term goals is to find an integration point with DuckDB's table implementation as the "node table". Conversely at some point DuckDB could implement all the join algorithms and LadybugDB's REL table in their code base.

For now, any talk of Graph on DuckDB is limited to DuckPGQ and the more recent entrant DuckGQL (both of which don't touch the storage layer which is the main reason why LadybugDB exists).

Re: AWS Acquires DuckLabs

#272

Post by Fervicus »

phainopepla2 wrote: post #226
Fervicus wrote: post #224

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?

DuckDB is for analytics, so OLAP instead of OLTP. If you're using the DB for normal transactions, stick with sqlite

Thanks, I gathered that much. I am curious what kind of stuff people are using it for, especially in their personal projects.

Re: AWS Acquires DuckLabs

#273

Post by tyre »

topaz0 wrote: post #250
MeetingsBrowser wrote: post #132

Earlier quoted context omitted.

> How much do you really need for generational wealth? Common definition is somewhere between 1.5 to 5 million per child.

Says who? Ive never heard this and can't find anyone saying this.

How much do you need for your children to not work or provide complete financial freedom (i.e. can buy a home, raise a family, etc. without thinking about the income of their job)? That is the "generational" in generational wealth.

You need more than $1.5m today should be $6m by the time they're 20. Depending on inflation, cost-of-living, tuition, etc. that might be enough.

People talking about generational wealth aren't saying, "what if they live a frugal life in the Topeka suburbs."

Re: AWS Acquires DuckLabs

#274

Post by shermantanktop »

solatic wrote: post #246
qaq wrote: post #70

Earlier quoted context omitted.

Man I admire AWS marketing team for convincing people DynamoDB is a very good product. 100 items max per Transaction BatchGet 100 items, 16 MB max low write limits on same key Item size 400 KB max etc.

DynamoDB has basically two legitimate use-cases that I'm familiar with: 1. You're selling a system to a customer to use within their own AWS account, that you will have no access to, and it needs a transactional datastore (not just an object bucket) of some kind. The fact that it costs nothing by default (particularly valuable when the customer is trying to deploy a proof-of-concept), scales more-or-less perfectly wi…

Anyone trying to use a kv store for relational workloads is The same kind of person who uses a kv cache with durability features instead of a kv store. You can’t blame the tech for their mistakes.

Re: AWS Acquires DuckLabs

#276

Post by Kinrany »

andriy_koval wrote: post #211
toast0 wrote: post #208

Earlier quoted context omitted.

Practicality and wisdom prevent trying to fill all the database niches with a single product. Even if you did it, I'd be surprised if a single code base is optimal across the spectrum from resource constrained microcontrollers all the way up to IBM Z Series mainframes and everything in between; along with the full spectrum of persistence from in-memory MRU (or similar) caching to full two phase global consensus as we…

> microcontrollers is a marginal niche, but everything else can be handled by one DB. You think we have PG with extensions (including duckdb) already covers most of the ground, making something like that distributed is also feasible task (there are projects), architecting system to make core engine embeddable is also feasible task.

Even microcontrollers would merely require custom compilations that turn off features.

There are no technical reasons for having more than one codebase, only economical and coordination-related.

Re: AWS Acquires DuckLabs

#277

Post by oblio »

Boxxed wrote: post #37

Can we stop consolidating everything under a handful of massive companies?

This will get a lot worse before it will get better. All the hyperscalers will inevitably drift towards total vertical integration.

Let's hope they never reach the "owning a private military" stage.

Re: AWS Acquires DuckLabs

#278

Post by jen20 »

pessimizer wrote: post #180
kccqzy wrote: post #140

Earlier quoted context omitted.

Red Hat grew on GPL licensed projects to become a $34 billion business. Canonical does the same except it’s Ubuntu not RHEL and charges more than Red Hat. You really underestimate the value of support contracts.

GPL is not MIT. If your software is GPL, you can sell it relicensed as MIT for income.

You can only do this if you own the copyright for all contributions.

Re: AWS Acquires DuckLabs

#279

Post by LPisGood »

nixon_why69 wrote: post #96
qaq wrote: post #70

Earlier quoted context omitted.

Man I admire AWS marketing team for convincing people DynamoDB is a very good product. 100 items max per Transaction BatchGet 100 items, 16 MB max low write limits on same key Item size 400 KB max etc.

The reason it's good is because, although it is bad, you never have to worry about it in terms of maintenance, admin or scale. It's like lambda for databases. For the same price, you can run a much more capable PSQL instance with way better features, but now you're on the hook for it being up 24/7.

You do have to worry about scale with lambda though. It’s not super hard to hit a rate limit where warm up times start being a real problem.

Re: AWS Acquires DuckLabs

#280

Post by shermantanktop »

cmiles8 wrote: post #33

Congrats to the founders but honestly feel bad for the team. Hearing so many not good things coming from inside AWS these days. Place sounds like a total mess. Seems like a constant stream of top talent fleeing on my LinkedIn this past year. I hope they just let the team carry on and don’t contaminate it with all the other craziness going on.

Does LinkedIn activity paint an accurate picture of wherever you work?

I can’t say that’s true for me and my company. It’s not all lies or anything, it’s a fragmented view that emphasizes conflict and the most visible 10% of what the company actually does.

Post reply on HN