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

The Operating Loop

How the platform decides what to materialise next, and why that is a governed change.

Editable source SVG draw.io All views
Usage telemetry query log, catalog hits Slow query analysis top 20 by cost Freshness class review with the data owner Cache or summary change one artefact Promotion through gates same pipeline as a view Measure the effect P95 and source load Materialisation loop what is actually used candidates agreed staleness revision new baseline next month's signals The Operating Loop — How the Platform Decides What to Materialise Next Materialisation is a governed change, not a tuning knob. A summary added without an owner agreeing its staleness is a correctness decision taken by an engineer. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Materialisation is a governed change, not a tuning knob. A summary added without the data owner agreeing its staleness is a correctness decision taken quietly by an engineer.
  • The loop starts from what is actually used, not from what is slow. A slow query nobody runs is not a problem worth a cache and a refresh job.
  • Every change to the freshness contract goes through the same promotion pipeline as a view change, so it is reviewable and reversible.

Cadence

  • Monthly, with the top twenty queries by total cost and the top twenty datasets by access count as the standing inputs.
  • The measurement step is mandatory: a materialisation that did not move P95 or source load is removed at the next cycle.

Risks

  • Materialisation accretes. Without the removal step the estate slowly becomes a cached hub with a virtualisation licence on top, which is the failure mode this architecture is most likely to reach by accident.
◀  Observability All views Cost Model  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source32-materialisation-loop