The question I get most often after talks, after podcast episodes, and in newsletter replies is a simple one: where do I start with your books?
It is a fair question, because the library has grown. Between the O'Reilly and Manning flagships and the self-published series, there are now more than fifty titles at books.alexmerced.com, spanning the data lakehouse, AI engineering, economics and philosophy, and even fiction. That is wonderful for depth and terrible for a first-time visitor staring at a catalog page. Nobody should read fifty books to answer one question, and different readers arrive with very different questions.
So this article is the guide I should have written a while ago: a map of the library organized by what you are actually trying to do. I will walk the flagship titles first, since they anchor everything, then match books to goals, whether you are learning Apache Iceberg, architecting a platform, wiring AI agents to data, leading a data organization, or just curious what a data person writes about when the laptop closes. I will lay out curated reading paths for the three most common journeys, point you to the material you can get free, and close with every way to follow the ongoing work, since the books are the deep end of a much larger stream of newsletters, videos, and articles.
One promise up front: this is a guide, not a sales page. Where a free resource serves you better than a purchase, I will say so, and where a book is not for you, I will say that too. The whole point of writing this many books is that each one has a specific reader. Let me help you figure out if one of them is you.
The Flagships: The Three Books That Anchor Everything
Three titles form the foundation of the technical library, and nearly every reading path routes through at least one of them.
Apache Iceberg: The Definitive Guide (O'Reilly), which I co-authored with Tomer Shiran and Jason Hughes, is exactly what the title promises: the comprehensive treatment of the table format at the heart of the modern lakehouse. It covers Iceberg's architecture from the metadata tree down, the mechanics of transactions, schema and partition evolution, time travel, row-level operations, and the practical work of using Iceberg from Spark, Flink, Dremio, and the wider engine ecosystem. If you have read my long-form articles on deletion vectors, the variant type, or streaming to Iceberg and wanted the full foundation underneath them, this is that foundation, organized and sequenced the way articles never can be. Pick this up if Iceberg is entering your life in any serious capacity: you are evaluating it, adopting it, operating it, or interviewing for a role that touches it.
Apache Polaris: The Definitive Guide (O'Reilly) does the same job one layer up the stack, for the catalog. It explains why the catalog became the control point of the lakehouse, how the Iceberg REST protocol works, and how Polaris delivers multi-engine governance: principals and role-based access control, credential vending, federation across existing catalogs, and the operational realities of running the catalog layer in production. Readers of my Polaris state-of-the-project article will recognize the territory, and the book is where the territory gets full treatment. Pick this up if governance, security, or multi-engine access is your problem: platform teams consolidating catalogs, security teams asked to bless a lakehouse, and anyone whose diagram has more than one query engine pointing at the same tables.
Architecting an Apache Iceberg Lakehouse (Manning) is the builder's book, and the one I recommend most often to working data architects. Where the Definitive Guide teaches you Iceberg, this book teaches you to design a complete platform around it: the storage layer, the ingestion layer with batch and streaming pipelines, the catalog layer, the federation layer, the consumption layer, and the operations that keep it all healthy, with the reasoning behind every trade-off, not just the blueprints. You build a working mini lakehouse along the way, ingesting from PostgreSQL with Spark and serving dashboards in Superset. It carries a foreword by Tim Berglund and generous words from people I respect enormously in this community. Pick this up if you are the person responsible for making the architecture decisions: the platform you are designing this year is the platform this book was written for.
If you only ever buy one of my books, buy whichever of these three matches your seat. Everything else in the library is either a step toward them or a step beyond them.
The Agentic AI and Data Series: For the Era We Are Actually In
Beyond the flagships lives a growing series of self-published deep dives, the Merced Books on Agentic AI and Data, written for the collision of the lakehouse world and the AI world that my article series chronicles weekly. These books move faster than traditional publishing allows, which is the point: this frontier changes quarterly, and the series is how I keep book-length treatment current with it.
The AI Lakehouse: Architecting Data Platforms for AI is the series anchor and the natural sequel to the Manning book. It takes everything the lakehouse architecture established and re-derives it for AI workloads: Iceberg for reproducible training with snapshot versioning and time travel, vector search inside the lakehouse with embedding storage and hybrid queries, semantic layers that give agents the vocabulary to generate accurate SQL, feature engineering with point-in-time correctness, governance for AI including PII management and regulatory compliance, and reference architectures scaled from startup to enterprise. If you have been reading my articles on semantic layers, context management, and agentic standards and thinking "I need this as one coherent design," this is that design.
AI Application Architecture: Patterns for Building Intelligent Systems and The AI Engineering Handbook: The Full-Stack Reference for Building Intelligent Systems serve the builders on the application side of the seam: the engineers wiring agents, retrieval, memory, and orchestration into real products. Between them they cover the patterns my agentic standards article maps at the protocol level, embeddings and RAG, knowledge graphs, agent memory, MCP-era tool integration, and the production concerns that separate demos from systems.
Agentic Analytics addresses the specific revolution inside my own field: what happens to business intelligence when autonomous agents become the analysts. It is the book-length version of the argument threaded through this whole article series, that governed data, semantic layers, and open catalogs are the prerequisites for AI you can trust with numbers.
And Lakehouse for Everyone is the on-ramp: the definitive plain-language guide to understanding and deploying the open data lakehouse, written for the reader who is not yet ready for manifests and metadata trees. It is the one I suggest gifting to the executive, the product manager, or the analyst who keeps asking what all this lakehouse business actually means.
The series continues to grow, with titles covering hands-on Iceberg with Python tooling, decoupled analytical foundations, AI-driven workflow practices, and more arriving steadily. The catalog at books.alexmerced.com is always the current index, filterable by category, with every title linking to where you can buy it.
Match the Book to the Mission
Now the part you actually came for: given what you are doing, what should you read? Here is the routing table I use when people ask.
You are learning Apache Iceberg for the first time. Start with Apache Iceberg: The Definitive Guide, and pair it with the free articles and my YouTube tutorials as you go hands-on. If you want a gentler runway first, Lakehouse for Everyone before the Definitive Guide is a perfectly honorable sequence.
You are designing or migrating a data platform this year. Architecting an Apache Iceberg Lakehouse is your book, full stop. Read the Definitive Guide alongside it when you need format depth, and add the Polaris guide when your design reaches the governance layer, which it will.
You own governance, security, or the catalog decision. Apache Polaris: The Definitive Guide, plus the catalog and federation chapters of the Manning book for the surrounding architecture. My Polaris and federation articles make good free previews of whether this territory is yours.
You are bringing AI workloads to your data platform. The AI Lakehouse, ideally after the Manning book if you are building the foundation simultaneously, or on its own if the lakehouse already exists and AI is the new requirement.
You are building AI applications and agents. The AI Engineering Handbook as the reference, AI Application Architecture for the patterns, and Agentic Analytics if your agents' job is specifically answering questions from data. Readers of my personal-versus-shared context article will find the book-length machinery here.
You lead a data organization, or need to bring leadership along. Lakehouse for Everyone for the shared vocabulary, Agentic Analytics for where the field is going, and honestly, the free newsletter for staying current, since strategy shifts faster than shelves do.
You are a student or career-changer aiming at data engineering. Lakehouse for Everyone, then the Definitive Guide, then build something small and real before touching the architecture book. The free resources below will carry you a long way before you spend a dollar, and I mean that.
You want to know how I think when it is not about data. The Economics and Philosophy shelf collects my writing on markets, liberty, and human cooperation, the thinking that also animates my Lovatarian newsletter, and the Fiction shelf is where the storytelling instinct that powers all the analogies in my technical writing gets to run without a word count. Browse both categories at the catalog site with the filters, and know that these are written for pleasure and reflection rather than certification. If you have ever enjoyed the mailroom clerks and sealed-box warehouses in my technical explanations, you already know I cannot resist a story.
Three Reading Paths, Sequenced
For readers who want a curriculum rather than a single pick, here are the three paths I recommend most, in reading order.
The Platform Architect's Path. Lakehouse for Everyone if you are newer to the space, then Apache Iceberg: The Definitive Guide for the format, then Architecting an Apache Iceberg Lakehouse for the platform, then Apache Polaris: The Definitive Guide for governance, and finally The AI Lakehouse for where your platform is headed next. Five books, and at the end of them you can design, defend, and operate the architecture this entire article series describes.
The AI Engineer's Path. The AI Engineering Handbook as your foundation, AI Application Architecture for system patterns, then The AI Lakehouse to understand the data platform your applications will stand on, with the Iceberg Definitive Guide as the reference you keep within reach. This path runs in the opposite direction from the architect's, application-down instead of storage-up, and meets in the same middle.
The Leader's Path. Lakehouse for Everyone, then Agentic Analytics, then the opening and closing chapters of The AI Lakehouse for the reference architectures and strategy framing, skipping the implementation depth without guilt. Pair it with the weekly newsletters and you will be the best-briefed person in your steering committee.
The Free Shelf: Read Before You Buy
I believe strongly in earning the purchase, so know that a substantial amount of this material is available free, and some of the flagship content itself can be obtained at no cost through sponsored editions.
The resources hub at resources.alexmerced.com collects the free copies currently available, which have included the Apache Iceberg Definitive Guide and the Polaris guide through Dremio's sponsorship, plus special editions on agentic AI, alongside tutorials, community links, event calendars, and my conference slides. My article series, the very series this guide belongs to, runs thousands of words of free deep-dive weekly across DataLakehouseHub.com, my blogs, and the newsletters. And my YouTube channel carries hundreds of walkthroughs and explainers at no cost beyond your attention.
The honest guidance: sample the free material first. If my way of explaining things works for you there, the books deliver that same approach with the depth, sequencing, and completeness that free formats cannot, and you will buy with confidence rather than hope.
How to Follow the Ongoing Work
The books are snapshots. The work is a stream, and here is every channel of it, so you can pick the ones that fit your habits.
For weekly depth in your inbox, the Substack at amdatalakehouse.substack.com carries the long-form work, including the Apache Data Lakehouse Weekly and AI Weekly newsletters that track the Iceberg, Polaris, Arrow, Parquet, and agentic AI worlds from the primary sources, dev lists and specs, the same sourcing behind this article series. On LinkedIn, the Data Lakehouse Bytes newsletter delivers the professional-feed version, and following me there catches the daily commentary between issues.
For watching and listening, the YouTube channel at youtube.com/@alexmerceddata is the video home for tutorials, explainers, and talks, and the Datanation podcast, on Spotify and the usual platforms, is the audio companion covering the data, lakehouse, and AI show week by week.
For reading around the web, I publish on Medium at @alexmercedtech, on dev.to, and across my own properties: alexmerced.com as the link hub, whoisalexmerced.com for the background, DataLakehouseHub.com for the community resource site, and IcebergLakehouse.com for the Iceberg-focused knowledge base. Conference-goers can find me on the circuit regularly, Data Council, Data Day Texas, Subsurface, and many more, and the slides land on the resources site afterward.
And for everything at once, books.alexmerced.com links onward to all of it, which makes it the one URL worth remembering from this entire article.
Questions I Hear Most Often
Do I need to read the books in order? No. Each book stands alone by design, with the reading paths above as suggestions rather than prerequisites. The one soft dependency worth honoring: the architecture books assume the format knowledge the Definitive Guide provides, so architects newer to Iceberg get more from the sequence than from skipping ahead.
Print, ebook, or O'Reilly platform? Whatever matches how you actually read. The flagships are available in print and digital through the usual channels including the O'Reilly learning platform, the self-published series lives on Amazon in both formats, and the free sponsored editions are typically digital. I am format-agnostic and royalty-indifferent on this: the read that happens beats the format that impresses.
How current are the books, given how fast this field moves? The flagships cover foundations that age slowly, metadata trees and transaction semantics do not churn quarterly, and the self-published series exists precisely to move at the frontier's speed, with updates as the ecosystem evolves. For anything spec-fresh, the v4 proposals, this month's releases, the newsletters and articles are the current layer, and I write them partly as living errata for the shelf.
Which single book for a team book club? Architecting an Apache Iceberg Lakehouse for platform teams, The AI Lakehouse for teams straddling data and AI, and Lakehouse for Everyone for mixed technical and business groups. All three generate the right arguments.
Will there be more? Always. The catalog page is the living answer, the newsletters announce every arrival, and if the past year of this article series is any indication, the subjects queue themselves faster than I can write them.
Closing Thoughts
Fifty-plus books sounds like a lot until you understand the project behind them: one explanation style, the same one running through every article in this series, applied at every altitude a reader might need, from a leader's first orientation to a spec contributor's reference, across the technology I have given this season of my career to and the wider questions that make the career worth having. The library is large so that your entry point can be exact.
So here is the whole guide in one sentence: find your seat in the routing table above, start with that one book, sample the free shelf first if you want proof, and let the newsletters carry you forward between volumes.
Browse the full collection, filter by category, and find your starting point at books.alexmerced.com.
Top comments (0)