Asset Notification Integration
Asynchronous boundary
Asset Service has no direct Notification Service client. It publishes shared lifecycle contracts through its outbox. Notification Service lists all six asset event names as supported and maps each to an asset notification intent.
Lifecycle payloads carry tenant, asset description/state, optional holder references, notes, and due date. Notification Service owns recipient resolution, template variables, configured channels, delivery, and its retry behavior. Asset Service does not verify final recipient availability or delivery success.
No signals exist for document changes, availability, workflow start, due reminders, maintenance, warranty, transfer, or disposal. Email/in-app specifics and delivery guarantees are not Asset Service capabilities.
Requires confirmation
Production ownership, authorization governance, operational policy, and future architecture require confirmation where the source does not enforce them.
Source References
microservices/src/contracts/Events/AssetLifecycleEvents.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/asset-service/Infrastructure/AssetDbContext.cs