Customer 360 Enterprise Data Platform — Denodo on Azure · View 23 of 39 · Runtime
Decisions
- Denodo reads the landed Delta table, not the Event Hub. Nothing in the logical layer is stateful, so a streaming outage shows up as staleness on one attribute rather than as a broken view.
- Events whose device identifier has not yet resolved to an enterprise customer go to a holding table rather than being dropped or attached to a guess. They join the 360 on the next resolution pass.
- Sessionisation happens once in the stream, not per query. Every consumer sees the same session boundaries.
Numbers
- 60 seconds from tap to queryable on the 360; 32 partitions sized for a 4,000 events per second peak.
- Silver activity retained 13 months; bronze landing 30 days.
Risks
- The holding table grows if device-to-customer resolution degrades. It is monitored as a quality metric, not just as a pipeline metric, because a growing holding table means the 360 is quietly under-reporting activity.
