Operations — how data is queried, observed, governed
Query
5 open standards for Query in a modern data architecture, each with an opinionated judgement: Adopt, Situational, Assess, or Caution.
Start with SQL.
Adopt 1 standard
The standard to reach for in new work. Proven, multi-vendor, clearly the default for its slot.
-
SQL
— Structured Query Language
The universal data query language; not a decision.
ANSI / ISO/IEC 9075
Situational 3 standards
The right answer in some contexts but not others. Pick deliberately based on the constraint.
-
Substrait
Cross-engine query-plan IR — pick when you're building or integrating engines that need a portable plan format; end users rarely touch it.
Substrait Project (independent; ASF-inspired PMC)
-
SPARQL
— SPARQL Protocol and RDF Query Language
Query RDF; right when your data lives in triples.
W3C
-
GQL
— Graph Query Language
Vendor-neutral property-graph query language — pick when your stack is already on graph databases.
ISO/IEC 39075:2024
Caution 1 standard
We'd avoid it for new work — superseded or fading, but still encountered in existing systems.
-
MDX
— Multidimensional Expressions
Multidimensional query language; surviving only in MS Analysis Services.
Originally Microsoft (1997); referenced by the XMLA specification
More in Operations
Operations covers how data is queried, observed, governed.
See Query in context
These standards are one panel of the interactive Data Landscape, which maps every open standard a modern data architecture is built on. The underlying data is a single JSON file; disagree with a judgement? Open an issue.