Skip to main content

Asset Consumer Landscape

Summary​

A verified inventory of who consumes asset events. Notification is the only confirmed event consumer. Asset-service is not currently an event consumer, though it holds a foundation ledger for a future subscription.

Audience​

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

Reference Content​

Consumer inventory​

ServiceConsumes asset eventsEvidenceClassification
NotificationYes — all six event namesEventNotificationResolver recognizes and maps themConfirmed consumer
Asset-service (self)NoProcessedIntegrationEvent table exists but no subscription is wiredFoundation (inbound not implemented)
WorkflowNo event consumptionHTTP callback boundary onlyNot an event consumer
DocumentNo event consumptionHTTP boundary onlyNot an event consumer
EmployeeNo event consumption in asset-serviceIdentifier-only references in payloadNot an event consumer
GatewayNoRouting surface onlyNot an event consumer

Confirmed consumer: Notification​

The notification resolver's recognized set includes AssetRequested, AssetAssigned, AssetReturned, AssetRejected, AssetLostOrDamaged, and AssetRetired. Each maps to an Asset.* template key. The notification event consumer subscribes to the shared integration-events exchange, declares its queue, and dispatches each delivery in its own scope. See Notification consumer.

Absent inbound consumption in asset-service​

AssetDbContext defines a ProcessedIntegrationEvent idempotency ledger, and its source comment states it is "for when this service subscribes." No subscriber, consumer hosted service, or inbound handler exists in asset-service in the verified source. Inbound event consumption by asset-service is therefore Not implemented at this stage.

Source References​

  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/asset-service/Infrastructure/AssetDbContext.cs

See Also​

Keywords​

  • Consumer landscape
  • Notification consumer
  • Inbound not implemented

Revision Information​

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