SpecsModelExplore
Overview
Actors
External Systems
Data Platform
Ingestion
Storage
Processing
Serving
Query Engine
Semantic Layer
Analytics UI
Governance
SpecsModelExplore
Serving
OverviewGuideLinks and Communications
IDproduct.serving
DescriptionQuery layer and APIs that expose curated data to consumers.
Keyserving
Typesystem
TeamQuery Platform
Ownerquery@dataplatform.example
Statusactive
TechnologiesTrino, Presto, Redis
Attributesfederation: lakehouse, interfaces: sql,metrics
Tags
Table of contents
Guide
Serving
System at a glance
Containers
How queries reach the data
Responsibilities
APIs
Related workflows

Guide

Serving

Serving is the read path of the platform. Analysts, dashboards and external API consumers never scan raw lake files directly — they submit SQL to the distributed query engine or request governed metrics from the semantic layer, which translates business definitions into warehouse SQL with row-level policies applied.

Responsibility in one sentence

Execute federated SQL over the lakehouse, cache hot results, throttle abusive queries, and resolve governed metrics into policy-aware SQL.

System at a glance

Could not build diagram for model "example-data-processing".

Containers

Query Engine

Trino/Presto cluster — plans, executes and caches distributed SQL over lake + warehouse.

Semantic Layer

Governed metrics and dimensions — one definition, many consumers.

How queries reach the data

Responsibilities

  • Distributed query planning, optimization and execution.
  • Result caching for hot dashboard tiles.
  • Per-user concurrency limits and query time budgets.
  • Metric-to-SQL resolution with dimension filters and grain.

APIs

Both containers expose REST APIs documented on their Overview tabs:

Related workflows

Live dashboard tiles query materialized stream outputs through the engine:

Analysts iterate in notebooks before publishing governed dashboard tiles:

Fair use

When a query exceeds its time budget, the Query Throttler kills it and suggests an equivalent semantic-layer metric instead.

Links and Communications

3 incoming links · 1 outgoing link

Incoming Links(3)

Source objectLabelLink typeRelationRaw idRequiredDescription
Data Analyst

example-data-processing.actors.analyst

actor
queries via—linksproduct.serving——
Storage

example-data-processing.product.storage

system
serves curated data to—linksproduct.serving——
Processing

example-data-processing.product.processing

system
publishes results to—linksproduct.serving——

Outgoing Links(1)

Target objectLabelLink typeRelationRaw idRequiredDescription
Analytics UI

example-data-processing.product.analytics_ui

system
powers—linksproduct.analytics_ui——