Five service owners realize six planning concepts

Context

The planning nouns cross some service boundaries. The design must preserve those nouns while making each implementation owner explicit.

Decision

Queries is implemented by five service modules; the query object includes Explorer lists, and the export object includes workspace packages under their respective service owners.

Alternatives Considered

Create objects for each table family: That would replace the product concepts with persistence boundaries.

Combine the services: Explorer and workspace exports already have distinct authorization, storage and deployment boundaries.

Consequences

The contracts identify which service implements each facet. Splitting workspace packages into a separate concept requires a planning decision.