Skip to main content

Performance Idempotency and Ordering

Summary​

Notification uses event identity in a unique processed ledger; duplicate identities are skipped.

Relay occurrence ordering applies only within fetched work. Equal timestamps, concurrent relay order, global/per-person ordering, tenant partitioning, and replay order are not guaranteed. Correlation/causation are not populated by current Performance mapping. Exactly-once is not confirmed.

Requires confirmation​

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

Source References​

  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs
  • microservices/src/notification-service/Infrastructure/NotificationDbContext.cs
  • microservices/src/performance-service/Application/Commands/AppraisalCommands.cs

Revision Information​

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