Jaco van der Laan
Active filters:Model Versioning ×Clear all

SCD2 Is Not Enough (Part 1) — The Bi-Temporal Foundation — From Snapshots to Deterministic…

Engineering Time in Data Platforms — A 3-Part Series From Snapshots to Deterministic Timelines: Engineering Time in Data Platforms Most data platforms believe they are historized. They are not. They store history — but they do not engineer time. In this three-part MDDE deep dive, we will move from: Basic SCD2 storage to bi-temporal standardization (this article) Timeline compression and deterministic integration (Part 2) Valuation reconstruction with impact-driven refresh (Part 3) This first article lays...
Read more

SCD2 Is Not Enough (Part 2) — Timeline Compression and Deterministic Integration

Series Context Merging Multiple SCD2 Timelines Without Explosion: ASOF Sampling, Gaps-and-Islands, and PIT Tables In Part 1, we standardized heterogeneous sources into controlled bi-temporal SCD2. Now comes the hard part. Once everything is SCD2… Joining them becomes dangerous. Each SCD2 table has its own change points. Consider a simple 360-degree customer view requiring three SCD2 sources: Combined timeline: 9 change points from just 3 sources with 3 changes each. Each change fragments the timeline. Add...
Read more

🧩 Evolving Metadata-Driven Data Models — From DDL Generation to Automated Schema Migration

How metadata-as-code principles extend beyond model generation to manage safe, automated, and traceable schema evolution in production How metadata-as-code principles extend beyond model generation to manage safe, automated, and traceable schema evolution in production In my previous article, we explored how conceptual and logical metadata can automatically generate physical data models — turning business meaning into structure and SQL. After publication, Kristian Poulsen asked a question that perfectly captures the next step in this journey:...
Read more

Structure vs Content in Model Versioning

Structure versioning deals with the shape of the data: tables, columns, relationships, and schemas. Content versioning deals with the meaning of the data: business rules, filters, derivations, and how values are interpreted. Both are equally important: Structure changes affect how systems read/write the data. Content changes affect how the same data values should be understood. The platform’s physical core (historization + integration layers) is a superset of all structures ever modeled. Columns and tables are...
Read more