Customer 360 Enterprise Data Platform — Denodo on Azure  ·  View 14 of 39  ·  Data

Data Flow

What is copied, what is only read, and the cadence on every arrow.

Editable source SVG draw.io All views
Sources Salesforce CRM SAP and Oracle ServiceNow CSM Web and mobile Capture Event Hubs Kafka protocol Debezium CDC 5 min Data Factory nightly extract Land and curate Bronze raw, 30 days Silver conformed, 13 months Gold analytical, 7 years Enrich Entity Resolution Zingg, nightly Quality Rules Soda Core Model Scoring CLV, churn Serve logically Denodo base views Denodo cache TTL per view Embedded MPP Presto over Delta Consume Power BI Agent Desktop AI Assistant Notebooks 5 min 03:00 daily no copy cached Data Flow — What Is Copied, What Is Only Read, and How Often External / third party Queue / topic Interface / broker Data store Application we own event / async batch synchronous The two gutter arrows are the point of the platform: profile and case data reach the consumer without ever landing in the lake. v 1.0 · owner Data & AI Global Practice · date 2026-09

Read the gutter arrows first

  • The two arrows that bypass the middle of the page are the platform's whole argument: profile and case data reach the consumer without ever landing in the lake.
  • Everything on the physical spine is there because it could not be federated — too large to scan on demand, too slow at the source, or not queryable at all.

Cadences

  • Digital events: continuous, 60 seconds end to end. ERP change data capture: 5 minutes. Batch extract and model scoring: nightly, 03:00.
  • Bronze holds 30 days, Silver 13 months for activity and 7 years for orders, Gold a daily snapshot.

Deliberate omissions

  • Reference data loads, the marketing extract and the consent feed follow the same nightly path and are left off to keep the page readable.
  • Retention and rebuild times are on view 15; freshness classes on view 17.