Customer 360 Enterprise Data Platform — Denodo on Azure · View 11 of 39 · Structure
Decisions
- Fourteen interfaces, one contract. No consumer holds a source credential, and no source is reachable except through an integration view.
- The crosswalk interface is marked never cached, which is a functional requirement rather than a performance note — see view 07.
- Purview pulls lineage from Denodo rather than Denodo pushing to Purview, so the enterprise catalogue cannot go stale silently when a pipeline fails.
Ownership
- We own every left-hand interface and the contract on it. We own none of the right-hand ones, which is why capability limits, quotas and vendor SLAs are on view 12 rather than assumed away.
- Salesforce and ServiceNow API call limits are the binding constraint on federated concurrency, not Denodo throughput.
Risks
- SaaS vendors version their APIs on their own schedule. Schema drift is a named failure mode on view 39 and is caught by CI, not at runtime.