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

Container Architecture

The deployable units, the technology in each, and what talks to what.

Editable source SVG draw.io All views
Azure — Customer 360 landing zone Edge and delivery Front Door and WAF TLS 1.3 Denodo Load Balancer JDBC and ODBC API Management quota, keys, JWT Denodo query tier — AKS node pools VDP Interactive 3 pods, BI and desktop VDP Data Services 2 pods, REST VDP Analytical 2 pods, science Embedded MPP Presto, 6 workers Denodo control tier Solution Manager licence, promotion Design Studio modelling Data Catalog search, certification Scheduler cache refresh State Cache Database PostgreSQL Flexible Metadata Database VDP catalogue ECID Crosswalk PostgreSQL Query Log Log Analytics Azure data platform Databricks SQL serverless warehouse Delta Lakehouse ADLS Gen2 Event Hubs Kafka protocol Unity Catalog lake grants Platform services Microsoft Entra ID Key Vault source credentials Azure Monitor metrics and logs Microsoft Purview enterprise catalogue Salesforce SAP S/4HANA Oracle Billing ServiceNow Marketing Cloud REST JDBC cache read offload Parquet scan OAuth REST refresh Container Architecture — The Deployable Units and What They Talk To Interface / broker Application we own Data store Queue / topic Security / platform External / third party synchronous batch Three VDP pools, not one cluster: a data scientist scanning three years of orders cannot take latency from the contact centre. Source credentials are drawn on view 35, not here. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Three Virtual DataPort pools rather than one cluster: interactive, data services and analytical. A data scientist scanning three years of orders cannot take latency from the contact centre because they are not on the same servers.
  • The Embedded MPP tier (Presto) sits beside Denodo rather than inside Databricks, so a large scan over Delta does not queue behind a warehouse workload it has no relationship with.
  • The control tier — Solution Manager, Design Studio, Data Catalog, Scheduler — is a separate deployment from the query tier and can be restarted without affecting a running query.

Assumptions

  • Denodo runs in containers on AKS. The licence is core-based, so pool sizing is a cost decision as much as a performance one — see view 33.
  • The cache and metadata databases are separate PostgreSQL Flexible Server instances, so cache churn cannot affect metadata availability.

Not on this page

  • Credential retrieval from Key Vault, which happens on every source connection — drawn on view 35 where it belongs to the identity story.
  • Failure domains and zone placement — view 28.
◀  Layered Architecture All views The Denodo View Hierarchy  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source09-container-architecture