Customer 360 Enterprise Data Platform — Denodo on Azure  ·  View 29 of 39  ·  Operations

Workload Isolation

Three classes with different latency contracts, and the one resource they still share.

Editable source SVG draw.io All views
One Denodo estate, three isolated workload classes Interactive — target under 2 s VDP Interactive 3 pods Connection pool 200 per source Query timeout 8 seconds Cache-first plans Data services — target under 2 s VDP Data Services 2 pods APIM quota 600 per minute Query timeout 5 seconds No ad hoc SQL published views only Analytical — minutes are acceptable VDP Analytical 2 pods MPP workers 6, autoscaled Query timeout 30 minutes Row limit 50 million Shared below the line, and therefore governed by quota Source connection pools per-class ceilings Cache database shared, sized for peak Metadata database read-mostly Licence cores the real ceiling capped at 40% priority share Workload Isolation — Why a Notebook Cannot Slow the Contact Centre Application we own Decision point Risk / gap Data store failure / alternate synchronous Isolation stops at the source. A single ERP connection pool is the one thing all three classes still share, which is why it is drawn as a risk and capped per class. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Interactive, data services and analytical workloads run on separate pools with separate timeouts, row limits and connection budgets. A notebook cannot slow the contact centre because it is not on the same servers.
  • The data services pool accepts published views only and no ad hoc SQL, which makes its latency predictable enough to sit behind a 2-second API contract.
  • The analytical pool is capped at 40% of any source connection pool, so a large scan cannot exhaust the SAP connections the contact centre needs.

Where isolation stops

  • At the source. A single ERP connection pool is shared by all three classes and is drawn as a risk for that reason. Per-class ceilings contain it; they do not remove it.
  • Licence cores are the real capacity ceiling, and they are shared. Adding a pool is a commercial decision as much as a technical one.

Numbers

  • Interactive: 3 pods, 8-second timeout, 200 connections per source. Data services: 2 pods, 5-second timeout, 600 requests per minute.
  • Analytical: 2 pods plus 6 MPP workers, 30-minute timeout, 50 million row limit.
◀  Deployment All views Environments and Delivery  ▶
Solution Architecture v1.0 · Data & AI Global Practice · 2026-09 · 39 views · Denodo Platform, Microsoft Azure and open source29-workload-isolation