PH Pedro Holanda On The New Stack Podcast

“I had my Clanker try it, and he actually suffered a bit. And I was like, okay, if the robots can't do it that easily, it seems like this is not an easy setup. And with DuckLake, it's one SQL query. It's really that simple.”

The New Stack Podcast · Hands-On Engineering Podcasts · November 2026

“I had my Clanker try it, and he actually suffered a bit. And I was like, okay, if the robots can't do it that easily, it seems like this is not an easy setup. And with DuckLake, it's one SQL query. It's really that simple.” — Pedro Holanda, The New Stack Podcast

Context

Asked when a team should pick DuckLake over Iceberg or Delta, Pedro Holanda describes how his AI agent ("Clanker") struggled to set up Iceberg. It treats agent-friendliness as a new test for data infrastructure.

Transcript

The New Stack Podcast Around 16:32 into the episode
Pedro Holanda

But for like the network scenario, we're really talking about a few axes of difference of performance. So that's literally where you should be going crazy about it.

Jennifer Riggins

So, yeah, when should a team choose DuckLake for its lake house? And I know you might think always, but when is a logical point to make that decision to start testing out and making that move? I

Pedro Holanda

just read my mind. I think it's always. I'm not even joking. Make your argument then. Now, I think there's one scenario that I find that the other lake house solutions can be a bit more interesting is that they have more adoption. And that's a fact. Like we're still quite new. I think DuckLake was initially released a year and a half ago. And these other solutions have been around for many years, right? So there's a lot of tooling. There's a lot of options of how you can operate with it. And DuckLake is a bit more limited still. But the adoption is growing. But in terms of performance, I don't really see a scenario where Iceberg or Delta could really have a better performance because the thing is your data can grow quite a lot. You could be talking about petabytes. But the difference is in the catalog. And the catalog doesn't grow at the same scale as the data. Your catalog might be a bit limited depending on the database system you're using, right? So Postgres might have not the best performance for…

Jennifer Riggins

He's challenging you in the comments. Oh, yeah. So, we've been talking about, you know, you've released a lot of stuff with 2. I mean, again, it's all over the office, very aspirational. Y'all are working very soon to 2.0.1. So, what is on that roadmap? What should we expect then? And maybe in…

Pedro Holanda

Yeah, so for DuckDB specifically, for DuckLake, not much. And for DuckDB as well, I think it's only going to be bug fix releases from these two versions. So the major BFI stuff features and whatnot, they come like in a, it will come from 2.1 for DuckDB. So from the 2.0.1 that will be coming, I…

Jennifer Riggins

Okay. And those aren't bad things. Sometimes, especially after you have a big release, you want to come back and hone it and emphasize stability. So that's totally fine. Also, people are still getting there.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from The New Stack Podcast