A rehearsal, told as a story · October 2026

Building a gaming lakehouse on USD 200 a month

Lumen Ridge is a fictional betting operator with an online casino, a sportsbook and a chain of retail betting shops. Before wiring up its real sources, the data team rehearsed the whole platform end to end on synthetic data, with two AI engineers, Claude and Codex, building and reviewing each other's work in public pull requests.

221.6Msynthetic rows landed (online 106.7M, retail 114.9M)
0duplicate keys across 25 Silver and Gold grain checks
53 sto build seven Gold daily summaries that match their facts exactly
USD 5.89actually billed by Azure in the first week (list-price value USD 45.87)

The storyline

The brief was blunt: seven sources (five APIs, a PostgreSQL database and a file feed), finance-grade reconciliation, and a budget of USD 200 a month with a kill switch at USD 190. Nobody wanted to discover on the real data that a pipeline double counts a bet, that a Power BI refresh takes twenty minutes, or that an idle network gateway quietly costs more than the compute.

So the team built a dress rehearsal. Two generators produced a dirty, realistic month of online play and retail shop activity, complete with late arrivals, re-sent files, conflicting versions and missing settlements. Everything else was real: Azure Databricks with Unity Catalog, Terraform, a budget with alerts, dbt, Power BI, a ClickHouse copy for comparison, and a GitHub repository where every change was argued over until both reviewers wrote AGREE.

The ebook follows that rehearsal chapter by chapter, from the first landed file to the scheduled teardown, with the figures, the costs and the mistakes left in.

Inside the ebook

  1. The brief and the budget
  2. Synthetic data that misbehaves
  3. The architecture
  4. Landing without duplicates
  5. Silver rules as data
  6. Gold and the 53-second summaries
  7. Reconciliation first
  8. What it cost, and why the bill disagreed
  9. Dev and prod
  10. Catalogue and reports
  11. Lessons for the real project
  12. Epilogue: switching it off