VOL. I — A CRASH COURSE ON DATA DESIGN PATTERNS Technology-Agnostic · Regulatory-Mapped · Enterprise-Grade ED · 2026

The Data Architecture
Pattern Catalogue.

Sixty-three composable, technology-agnostic design patterns across the data lifecycle — ingestion through destruction — mapped to seventeen foundational, architectural, and operational principles, with comprehensive regulatory standards tracing.

63 Patterns 7 Lifecycle Stages 17 Principles 22 Standards Frameworks 3-Tier Progressive Depth

01 · How to Read

Patterns are indexed by a two-dimensional coordinate system: principle (row) and lifecycle stage (column). Each cell reveals one or more composable patterns. Click any pattern to progress from concise sketch to medium treatment to deep reference.

02 · Legend

Foundational Architecture Operational

IDs follow [PRN-stage-seq] — principle code, lifecycle stage abbreviation, sequence within cell.

03 · Standards Mesh

Every pattern traces to BCBS 239, MAS FEAT/TRMG, HKMA GL, GDPR, PDPA, EU AI Act, NIST AI RMF, DAMA-DMBOK, DCAM, ISO 8000/27001/27701/38505, SOC 2, and BNM RAI. Mappings are indicative, not legal opinion.

I.

The Matrix.

17 Principles × 7 Lifecycle Stages
63 Pattern Coordinates

Each cell is an intersection of a governing principle and a lifecycle stage. Tap any chip to open the pattern — or browse the full catalogue via the tab above.

◈ Hatched cells = no pattern at this intersection (by design) ◈ Hover for pattern title · click to open
II.

Pattern Catalogue.

Filter · Browse · Expand
III.

Index.

All 63 patterns · sortable
IDPatternPrincipleLifecycleOne-Line Intent
IV.

Standards Reference.

Regulatory & industry frameworks

Every pattern carries a standards mesh pointing to articles, principles, or controls it helps satisfy. Below is the consolidated reference set.

V.

Colophon.

Design philosophy

Why Patterns?

Microservice architecture matured once its patterns were codified. Data architecture has lagged — not for lack of practice, but for lack of vocabulary that is simultaneously technology-agnostic, composable, and regulatorily traceable.

This catalogue treats each design decision as a reusable primitive — a named solution to a recurring problem in a specific context — rather than as a product feature. Golden Source of Record is a pattern; a specific MDM vendor is an implementation.

The matrix is not a scorecard. Some cells are empty by design: the intersection simply does not manifest as a recurring architectural concern.

How to Use This

Read horizontally to discover how a principle plays out across the lifecycle. Read vertically to see what governance a stage must satisfy. Read diagonally to find emergent compositions — e.g. Contract-First Ingestion + Semantic Product Interface + Rail-Level Observability forms a reference architecture for a data product.

Every pattern has three depths: a sketch (card), a reference (modal body), and a mapping (standards grid). Start shallow. Deepen only when implementing.

Standards mappings are indicative. Legal interpretation requires counsel.

Attribution Note

This catalogue draws on patterns named variously across industry literature (DDD, EIP, DMBOK, Data Mesh, risk-data aggregation). Where a pattern has a widely recognised name, it is used. Where conventions conflict, the more general name is preferred. No proprietary methodology is reproduced.