Skip to main content

Asset Integration Reference

Summary

The asset-service is a hub with several inbound and outbound integrations: identity and tenant context on the way in, workflow and document services on the way out, an event bus feeding notification, and a gateway that fronts both the native and compatibility surfaces. This page presents them as a matrix with direction, protocol, ownership, data exchanged, auth evidence, failure boundary, and maturity.

Audience

Solution architects mapping the system context, developers wiring integrations, and support engineers diagnosing cross-service failures.

Reference Content

Integration context

Integration matrix

IntegrationDirectionProtocolOwnershipData exchangedAuthFailure boundaryMaturity
Employee/userReference(payload only)asset-serviceIdentifier-only referencen/aNo client; no FKIdentifier-only
IdentityInboundHTTPIdentityJWT (multi-key)JWT multi-keyAuth rejectionImplemented
TenantInboundHTTPGateway/serviceForwarded headers/claimsClaims400 if missingImplemented
WorkflowOutbound + inboundHTTPWorkflowRequests + callbackFeature-flaggedFlag-gated; 409 on direct while managedTransitional
DocumentOutboundHTTPDocumentBytes external, references localService call503 fail-safeTransitional
NotificationDownstreamEventNotificationLifecycle payloadsEvent busAt-least-onceImplemented consumer
GatewayFrontingHTTPGatewayReverse proxy + compat slice + ESS by labor idForwardedFeature-flagged sliceTransitional
MessagingOutboundEventasset-serviceOutbox-relayed eventsn/aUnbounded retry, no DLQTransitional
DatabaseOwnedDBasset-servicePersisted aggregate + logsConnectionApplication-level tenant isolationImplemented
Compatibility UIFrontingHTTPasset-serviceMonolith-shaped requestsTenant-scopedMapping errorsTransitional

Source References

  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • microservices/src/contracts/Events/AssetLifecycleEvents.cs
  • microservices/src/gateway-api/Program.cs

See Also

Keywords

asset integrations, workflow, document, notification, gateway, messaging

Revision Information

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