Customer 360 Enterprise Data Platform — Denodo on Azure  ·  View 02 of 39  ·  Context and scope

High-Level Architecture

The shape of the platform in one picture: federate by default, materialise by exception.

Editable source SVG draw.io All views
Sources Salesforce CRM SAP S/4HANA ServiceNow CSM Digital Events Move only what must move Azure Event Hubs Kafka protocol CDC and Batch Load Debezium, ADF Delta Lakehouse ADLS Gen2 Resolve identity Entity Resolution Zingg on Spark ECID Crosswalk PostgreSQL Denodo logical layer Virtual DataPort federated engine Semantic Model Customer360 Cache and Summaries PostgreSQL, MPP Delivery JDBC and ODBC REST and GraphQL API Management Azure APIM Consumers Power BI Agent Desktop AI Assistant Notebooks clickstream nightly join key High-Level Architecture — Federate by Default, Materialise by Exception External / third party Queue / topic Interface / broker Data store Application we own event / async batch synchronous Only digital events, deep history and model output are physically moved. Profile, order and case attributes are read where they live. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Federation is the default and physical movement needs a justification, not the other way round. Copying five systems into a hub was rejected: it adds a pipeline, a storage bill and a staleness window to data that is already correct where it sits.
  • Only three things move — digital events, deep order history, and model output — because each is either too large, too slow or not queryable at the source.
  • The identity crosswalk sits between the lakehouse and Denodo, not inside either, so the mastering logic can be tested against a labelled set on Spark.

The alternative considered

  • A physical customer hub in Databricks with everything landed. Cheaper per query, but every attribute inherits an ETL latency, and a profile correction takes a batch cycle to appear on an agent's screen.
  • Chosen instead: federation for the operational attributes an agent reads, materialisation for the analytical ones a report aggregates.

Numbers

  • Customer profile query target under 2 s, full Customer360 under 5 s, API response under 2 s at P95.
  • 500 concurrent sessions, 99.9% availability, RTO 30 minutes, RPO 5 minutes on the crosswalk.
  • Digital activity visible on the 360 within 60 seconds of the tap that produced it.
◀  System Context All views The Governing Principle  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source02-high-level-architecture