Customer 360 Enterprise Data Platform — Denodo on Azure · View 18 of 39 · Data
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.