Customer 360 Enterprise Data Platform — Denodo on Azure · View 08 of 39 · Structure
The layering rule
- Dependencies point downward only. A base view never references another base view, and a business view never references a source.
- Security, classification and quality flags are declared once at the integration layer. Every business view created above it inherits them on the day it is created, which turns the layering rule into a security control rather than a style guide.
- The rule is enforced by the VQL lint in the promotion pipeline, not by review discipline.
Why security is not a layer
- Drawing governance as a vertical band beside the stack is the common form and it is misleading: it suggests a component that intercepts calls. Here it is a property of layer 2 that propagates upward with the views themselves.
Deliberate omissions
- One representative arrow per boundary rather than the full call graph; a layered view is about the direction of dependency.
- Roughly 40 base views and 18 integration views exist; five of each are shown.
