Performance Consumer Landscape

Summary

Audience

Developers, QA and support engineers, integration reviewers, solution architects, and implementation partners.

Reference Content

Notification Service is the only confirmed direct consumer and subscribes to all seven contract types.

Workflow is HTTP-only. Gateway is an infrastructure/compatibility boundary. The other named services have no confirmed Performance consumer. Totals: one consumer service and seven event-type subscriptions; HTTP relationships are excluded.

Requires confirmation

Operational ownership, service objectives, reconciliation, replay, and future consumer governance require confirmation where not explicitly implemented.

Related Articles

• Performance events documentation
• Event overview

See Also

• Performance technical documentation
• Performance database documentation

Keywords

• Performance events
• Integration contracts

Source References

• microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/notification-service/Application/NotificationDispatcher.cs

Revision Information

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