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

The Freshness Contract

Which attribute groups are federated, cached or materialised — and the rule that decides, rather than the author.

Editable source SVG draw.io All views
Freshness required Access strategy Where it materialises Refresh trigger Customer profile Near real time Federated Nowhere Not applicable Contact details Near real time Federated, masked Nowhere Not applicable Account status Near real time Federated Nowhere Not applicable Orders, last 90 days Near real time Federated Nowhere Not applicable Order history, 3 years Daily MPP over Delta Silver tables Nightly ELT Open support cases Under 15 minutes Partial cache Cache database Scheduler, 15 min Marketing engagement Under 1 hour Full cache Cache database Scheduler, hourly Digital activity Under 60 seconds Federated on Delta Silver streaming Continuous Lifetime value, scores Daily Federated on gold Gold tables Model run, 03:00 Aggregated KPIs Daily Denodo summary Summary table After model run Identity crosswalk Immediate Federated only Never Merge event Freshness Contract — What Is Federated, Cached or Materialised, and Why This table is the architecture, not a tuning guide. A view author cannot choose a strategy; they declare a freshness class and the platform assigns one. v 1.0 · owner Data & AI Global Practice · date 2026-09

This table is the architecture

  • A view author cannot choose an access strategy. They declare the freshness their consumer needs and the platform assigns federation, cache, summary or lakehouse materialisation.
  • Removing that choice is what stops the estate drifting into either everything cached, which is a stale hub, or everything federated, which is a distributed join on every dashboard refresh.
  • Changing a row is a governed change with the data owner in the room — view 32 is the loop that does it.

The two rows that matter most

  • Customer profile is federated with no cache anywhere. An agent correcting an address must see it on the next call, and no TTL short enough to guarantee that is cheap enough to run.
  • The identity crosswalk is never cached at all. Caching it would make a merge invisible for up to a day, which is exactly the failure the steward journey found.

Assumptions

  • Freshness numbers were agreed with the contact centre and the reporting community, not derived from what the sources happen to support.
  • Where a source cannot meet its declared freshness, the answer is a cache with a published staleness, never a quietly slower view.
◀  The Customer 360 Logical Model All views Caching and Acceleration  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source17-freshness-and-materialisation