Apache Iceberg's Write-Audit-Publish (WAP) pattern enables data teams to validate changes in isolated branches before promoting to production. This approach eliminates the need for duplicate UAT environments, reduces storage costs by up to 30%, and cuts release costs by up to 99% by writing data once and reusing it across test and production. The workflow involves creating temporary branches, performing validation checks, and fast-forwarding metadata to production without file rewrites or downtime.
Table of contents
EXPEDIA GROUP TECHNOLOGY — DATAA strategic shift toward data flows that are version-controlled, testable, and auditableWhat is Write‑Audit‑Publish?A different approach with Iceberg WAPWAP: Generic vs Iceberg comparisonWhy this mattersKey benefits:Step-by-step implementationExtending branch retentionGet Vincent DANIEL’s stories in your inboxWhy drop a branch?Why disable WAP?Lightweight auditing with historical tagsDisadvantagesCost Savings in Practice: Expedia GroupFinal thoughtsFurther reading368 Impressions