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

The Denodo View Hierarchy

The four modelling layers, the naming standard, and where each kind of logic is allowed to live.

Editable source SVG draw.io All views
Physical sources Salesforce SAP S/4HANA ServiceNow Delta Lakehouse Layer 1 — base views bv_sf_account no logic bv_sap_kna1 no logic bv_snow_case no logic bv_lake_clv no logic Layer 2 — integration views iv_customer ECID, survivorship iv_customer_order iv_customer_case iv_customer_value Layer 3 — business views Customer Profile Customer Orders Customer Support Customer Value Layer 4 — the 360 Customer360 certified Published SQL endpoint REST resource GraphQL schema renames publishes The Denodo View Hierarchy — Four Layers, One Naming Standard External / third party Data store Application we own Interface / broker synchronous Base views carry no transformation and no business name. Security is declared once at layer 2, so no consumer can reach a source structure that has not passed through it. v 1.0 · owner Data & AI Global Practice · date 2026-09

The standard

  • bv_ base views carry no transformation, no business naming and no filtering. They are a one-to-one projection of the source structure and nothing more.
  • iv_ integration views own normalisation, the enterprise id join, survivorship and the quality flags. This is the only layer where a source name may appear in a join.
  • Business views own naming and nothing else. Customer360 composes business views and adds no logic of its own — it is a contract, not a query.

Why the discipline is worth the extra layer

  • The alternative, letting business views read base views directly when it is quicker, works until a source changes. Then the impact analysis returns forty views instead of four, and the policy declared at layer 2 has been bypassed by whoever took the shortcut.

Numbers

  • Roughly 40 base views, 18 integration views, 9 business views, one Customer360, three published endpoints.
  • A new source is expected to add base views and at most one integration view — never a business view.
◀  Container Architecture All views Integration Surface  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source10-denodo-view-hierarchy