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

Caching and Acceleration

What can answer a query, how each store is kept fresh, and where the platform refuses to help.

Editable source SVG draw.io All views
Request Customer360 query SQL or REST Planner decides Cache still valid? Summary covers it? Source can delegate? Served from Cache tables PostgreSQL Summary tables pre-aggregated MPP over Delta Presto workers Source system delegated SQL Kept fresh by Denodo Scheduler per-view TTL Incremental refresh on change column Merge event listener ECID changes Bounded by Never-cache list crosswalk, consent Stampede control single refresher Stale-read budget declared per view hit delegate invalidate Caching and Acceleration — What Answers a Query, and What Keeps It Honest Application we own Decision point Data store External / third party Queue / topic Risk / gap synchronous failure / alternate A cache miss is a latency event; a stale cache after a merge is a correctness event. Only the second one is drawn in red. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Four things can answer a query — cache, summary, MPP over Delta, or the source itself — and the planner chooses by cost, not by a hint in the view.
  • Incremental refresh on a change column wherever the source exposes one; full refresh only where it does not. Full refresh of a large cached view during business hours is a source outage waiting to be scheduled.
  • A single refresher per cached view, so a cold cache under load cannot turn into a stampede against the source.

The red arrow

  • A cache miss is a latency event and is drawn in grey. A stale cache after a merge is a correctness event and is drawn in red — the platform treats them as different classes of failure and only one of them pages anybody.

Numbers

  • Cache TTLs run from 15 minutes for support cases to 24 hours for reference data; the never-cache list holds the crosswalk, consent and every financial column.
  • MPP offload triggers above roughly 10 million rows scanned; below that the federated path is faster than the handover.