Skip to main content

Getting Hands-On with Apache Iceberg: From Docker to AWS in a Day

Image
By

 
On Tuesday this week, I was back at AWS on Holborn Viaduct learning about Apache Iceberg with a colleague. Iceberg is a table format standard for managing large-scale datasets and their metadata. The AWS-managed approach is to store the data in S3, meaning you only pay for storage and bandwidth. Other tools, such as Apache Spark, can then be used on top to build a data warehouse - or in this case, a Lakehouse. AWS also supports self-hosting, but this requires you to configure and manage aspects such as maintenance yourself.

One of the major advantages Iceberg has over other data warehouses is its support for True ACID transactions, and its table format standard means you don’t have to run a database engine. Anything which wants to access the data can go straight to S3. As a software engineer with a background in object orientation, this feels potentially brittle and a coupling nightmare, but I am sure it works in practice.

 

The pre-workshop presentations made Iceberg feel simple and easy to use with lots of ways to get data in and out, such as SQL, Zero ETL, REST, batch and streaming. It can be easily integrated with RDS (Postgres, etc), AWS Lambdas, DynamoDB, Redshift and more, in near real time, with services such as AWS Firehouse. 

Something which stood out for me is that every time a dataset is updated, a full copy of the database is made and stored. This can happen up to 60 times an hour. That’s a lot of data. This is why it’s important to have maintenance configured so that storage doesn’t become unmanageable, or worse, expensive. 

The AWS presenters were great and really easy to listen to, as was the customer panel. However, I really couldn’t wait for the afternoon's workshop, so I started playing by myself while I was listening.

In about 20 minutes, with a little help from Claude Code, I had Apache Iceberg up and running in docker containers on my Linux laptop, and was able to create tables, and insert and query data with Spark. I was keen to prove I could access the data programmatically, so with more help from Claude I created a RESTful catalog and was able to use Curl to query pages of data.

 

I’m a massive Digital Ocean fan, so initially I had Claude create Terraform to run Iceberg in a droplet and its S3 compatible storage. However this would mean paying about $40 a month just to run the droplet, so I asked Claude to generate the Terraform for AWS instead. This brought the cost down to next to nothing, for small payloads at least.

The afternoon workshop came quite late, mostly due to the knock on effect of starting late due to train strikes and questions asked in the earlier sessions. I love AWS workshops, they’re one of the highlights of the AWS Summit for me. However, there is often a lot of “copy this here”, “configure this service like this”, “push this button and hope it works”. Unfortunately it didn’t for me on this occasion. What would be great to see instead is how to create the Terraform to create, configure and integrate Apache Iceberg in AWS, but I know most people point and click in the AWS console.

However, that didn’t detract from what was a really interesting, useful day where I learnt a lot.


 

 

Comments

Post a Comment

Popular posts from this blog

It's great to be back at the ACCU Conference 2025!

By
Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...
1 comment
Read more

I, Robot

By
The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...
1 comment
Read more

Write Your Own Load Balancer: A worked Example

By
I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...
Post a Comment
Read more