Untitled design (21)

Tim Berglund

VP Developer Relations

Gilles Philippart profile picture  (round 128px)

Gilles Philippart

Software Practice Lead

In this episode, Tim Berglund breaks down the Iceberg catalog: the layer that maps table names to metadata files so engines like Spark and Trino can find your data, guarantee atomic commits, and handle concurrent writes safely. You’ll see how the Iceberg REST Catalog spec enables portability across implementations like Polaris, Unity Catalog, and others, and why your catalog choice shapes what’s possible in your data lake.

Do you have questions or comments? Join us in the #developer-confluent-io community Slack channel to engage in discussions with the creators of this content.

Be the first to get updates and new content

We will only share developer content and updates, including notifications when new content is added. We will never send you sales emails. 🙂 By subscribing, you understand we will process your personal information in accordance with our Privacy Statement.