
Follow Sarah’s crisis of three compute engines, Snowflake, Databricks, and S3, and learn how one storage, many engines, one truth architecture fixes cross-engine questions and aligns the data.
The 2024–2026 inflection points reveal a rapid shift to a single interoperable iceberg ecosystem, with Polaris and Unity catalogs enabling cross-engine reads and one governance layer across three engines.
Apache governance with distributed committers and a public process, ensuring open collaboration, vendor independence, and robust architecture against dominant vendor strategy changes.
Bridge the first two modules by reframing the lakehouse and outlining five key insights. Compare Iceberg, Delta, and Hoodie, emphasize governance, and prepare for the spec internals exploration.
Understand how Iceberg turns raw parquet files into a queryable table via a five-layer stack: catalog, metadata.json, manifest list, manifests, and parquet data, enabling fast pruning and time travel.
Explore how Iceberg uses manifest files as a metadata index to prune data at query time, using Avro manifests with per-file and per-column statistics and status flags.
Understand how a manifest list ties each snapshot to its manifests, and how the snapshot tree with parent links enables reading audit log in Spark, expire snapshots to control storage.
Discover how Iceberg replaces Hive partitioning with hidden, function-based transforms that prune by date and id, and how you can evolve partition strategies without rewriting data.
Unify engines through a single REST catalogue driven by a versioned OpenAPI spec inside Apache Iceberg, enabling any engine to attach with unified auth and a shared protocol.
Apply governance with a three-level model—identity, namespace, and table—by aligning grants, naming conventions, and authentication patterns to manage access and operations.
Explore Unity Catalog open source, a lineage-capturing data catalog for Delta and Iceberg, enabling multi-engine access via direct Iceberg REST or Uniform, ideal for Databricks-centric teams.
Set a target file size and distribution mode (hash or range) at table creation to prevent small files sprawl in iceberg writes. Use write-time and maintenance compaction to protect performance.
Coordinate parallel Flink writers with a single coordinator to commit at each checkpoint, balancing freshness, file counts, and operational maintainability in Iceberg sinks.
Learn upsert patterns with merge in Apache Iceberg, using Bronze CDC and Silver Current to keep a single source of truth with incremental, idempotent merges and row_number for latest events.
Apache Iceberg won the table-format war. Now you have to actually run one in production.
Most tutorials show you a CREATE TABLE and call it a lakehouse. This course takes you all the way: the spec internals, every major catalog, all the write and read engines, and the production discipline that separates a weekend pilot from a platform 200 engineers depend on.
Across 23 modules and 116 lessons (~12.5 hours), you'll follow Sarah — a Head of Data Platform running shared Iceberg storage across three continents — as she makes the decisions you'll soon make yourself. You'll read the spec as a working mental model (manifests, snapshots, metadata.json, the commit protocol), then choose a catalog with a real Decision Spine matrix comparing Polaris, Unity OSS, Nessie, Glue, and Hive Metastore — and defend the choice.
From there you build: a complete medallion lakehouse with Kafka CDC into bronze, Spark MERGE plus write-audit-publish into silver, and multi-engine readers (Trino, Snowflake, DuckDB) on gold. You'll run the maintenance nobody teaches — compaction, expire-snapshots, orphan cleanup, rewrite-manifests — with real cost numbers, and master branching, tagging, and time-travel rollback patterns that auditors and SREs sign off on.
What makes this course different
You'll learn to
Who's teaching
Built by Snowbrix Academy and taught by Amit — a credentialed practitioner (SnowPro Core, 2x Databricks-certified) who builds production data platforms for a living. Every pattern here is one you can defend on Monday.
If you're a data engineer ready to own the lakehouse — to stop following table-format tutorials and start architecting and operating one — this is your course.