Customer 360 & Real-Time Risk Intelligence Platform · View 03 of 20

Layered Architecture

What depends on what. Dependencies point downward only; platform services are consumed by every layer above them.

Editable source SVG draw.io All views

Dependency rule

A layer may call the layer directly below it, never the one above
Consumption never reaches past serving into storage — no direct lake reads for BI
Curation logic lives in code, not in BI tools, so it is testable and reusable

Why layered at all

Lets storage technology change without touching consumption contracts
Makes the blast radius of a change explicit before it is made
Gives each layer a distinct owning team and a distinct on-call rota

Known tensions

Low-latency risk consumers bypass the warehouse and read gold topics directly
That shortcut is explicit and contract-governed, not an accidental coupling
Feature store spans serving and curation; it is owned by the curation team