liveBook · Manning

Data quantum

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A data quantum is the smallest independently deployable unit of data architecture that packages data with the capabilities needed to discover, govern, observe, onboard, and consume it.

A data quantum is the smallest deployable data product that delivers value within a single domain. It packages interoperable data with discovery, governance, observability, onboarding, and control capabilities, making a focused alternative to an enterprise-wide data lake. section 14.2.2 section 14.3.2

Treat a data quantum as five coordinated subcomponents:

  • Discovery and dictionary services expose passive metadata, descriptions, lineage, and access information. section 14.3.2
  • Observability services expose availability, schema changes, and data-quality measures as active metadata. section 14.3.2
  • Control services provide APIs for dataset versions, onboarding, storage, and data-quality rules. section 14.3.2
  • Data onboarding brings source data into the quantum under controlled quality and lifecycle practices. section 14.3.2
  • Interoperable data allows consumers and other data products to use the quantum as a composable unit. section 14.2.2 section 14.6

Start with six focused datasets

A small implementation used six datasets, each consisting of one table with fewer than 200 columns. Delivering this narrower product first produced value quickly, while leaving room to evolve features from customer feedback and a backlog. section 14.2.2 section 14.3.1

Figure 14.4 The data quantum takes the shape of a hexagon, highlighting its multiple endpoints, allowing access to data, metadata, observability, and control.

Use the hexagonal model to inspect the quantum through its data, metadata, observability, and control endpoints. section 14.2.2

Figure 14.7 A data quantum (pl. data quanta) is the implementation of a data product and is represented as a hexagon.

Use the logical architecture figure to relate the data product to its discovery, observability, control, onboarding, and interoperability capabilities. section 14.3.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains the five-part logical architecture and iterative minimal-product approach, while stopping short of detailed implementation instructions.
Examples
Uses six small datasets, each with one table and fewer than 200 columns, as an incremental delivery example.
What it assumes
Assumes familiarity with data architecture and data mesh principles while establishing the quantum concept from its deployment role.
What you can do after
Build it incrementally as a minimal data product, then expand capabilities through customer feedback and a backlog.
How it connects
Connects data products to data mesh, data contracts, domain ownership, self-serve data platforms, and federated computational governance.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.