Skip to main content

Asset Document Boundaries

Summary​

Document integration is an HTTP boundary to the document service. It is not part of the asset event model; no document integration contract is produced or consumed by asset-service.

Audience​

Engineering, integration, QA, architecture, and security reviewers.

Reference Content​

HTTP, not eventing​

DocumentServiceClient is a typed HttpClient that stores and retrieves document bytes in the document service; asset-service keeps only document references in its own schema. These calls are request/response HTTP, not events. No Document* event is produced or consumed by asset-service.

What asset-service holds versus what it calls​

DataLocationMechanism
Document bytesDocument serviceHTTP call
Document reference metadataAsset schema (AssetDocumentReferences)Local persistence

No document event on the asset side​

Attaching or removing a document reference is a local persistence change. It does not raise an asset domain event and does not emit an integration contract. The six asset lifecycle events are the only events asset-service produces.

Public-safety note​

Document identifiers, filenames, storage locations, and service addresses are intentionally excluded.

Source References​

  • microservices/src/asset-service/Infrastructure/DocumentServiceClient.cs
  • microservices/src/asset-service/Infrastructure/AssetDocumentGateway.cs
  • microservices/src/asset-service/Program.cs

See Also​

Keywords​

  • Document boundary
  • HTTP integration
  • Reference only

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly