Architecture Patterns Deep Dive

Part 2: The Architecture Landscape

Part 1 built the vocabulary and physics an architect reasons with — ACID and CAP, OLTP vs OLAP, batch vs NRT vs RT. Part 2 turns that vocabulary into named, arguable shapes: the six patterns in this group are the actual whiteboard sketches an architect defends in a design review, each one a specific bet about how to reconcile latency, storage economics, curation, and ownership. Taken together, the seven topics here aren’t seven independent tools to memorize — they form a landscape with real structure: two answer how data gets processed (Lambda, Kappa), two answer how it’s stored and curated (Lakehouse, Medallion), two answer who owns it and how it’s found (Data Mesh, Data Fabric), and the closing topic shows how those three axes combine into one real system rather than a single pick from a menu.

mindmap
  root((Architecture Patterns Deep Dive))
    Lambda Architecture
      Batch + speed layers, reconciled at query time
    Kappa Architecture
      Stream-only, replay the log instead of a batch layer
    Lakehouse Architecture
      Open table formats add ACID to object storage
    Medallion Architecture
      Bronze/Silver/Gold, trust level legible by layer
    Data Mesh
      Domain ownership, data as a product
    Data Fabric
      Active metadata, automated discovery across a heterogeneous estate
    Choosing Among the Patterns
      Decision matrix across all six

See also: Lakehouse Architecture: Unifying Warehouse & Lake connects to Table Formats: Delta vs Iceberg vs Hudi in the Storage & Table Formats group, which goes deeper on how Delta, Iceberg, and Hudi differ.

Topics


| ← Previous: Choosing an Architecture & the Road to Becoming a Data Architect | Next: Lambda Architecture: Batch + Speed Layers → | |:—|—:|


Table of contents


Back to top

Independent, self-authored data architecture field notes.

This site uses Just the Docs, a documentation theme for Jekyll.