Mimir

← Back to documents

Pull Request: Harden Notification Service retry and idempotency path

github
notification
6c0379b051cb

github/pr-gh-5018-notification.md

Pull Request: Harden Notification Service retry and idempotency path

ID: GH-5018 Date: 2026-01-25 Repository: acme-commerce/notification-service Service: Notification Service Owner: Engagement Platform Status: merged Type: pull request

Summary

This pull request tracks production-readiness work for the Notification Service. The concern is related to stale cache entries surviving a blue-green release. The implementation area touches API contracts API-NOTIFICATION-01, API-NOTIFICATION-02, service telemetry, and operational runbooks.

Engineering Notes

  • Validate that retries are bounded and idempotency keys are respected.
  • Add structured logs with service, correlation_id, and customer_impact fields.
  • Confirm dashboards show p95 latency, error rate, dependency saturation, and queue depth.
  • Cross-service impact should be reviewed with Checkout Service, Billing Service, Inventory Service, Authentication Service, and Notification Service owners when applicable.

Acceptance Criteria

  1. Contract tests cover expected and malformed payloads.
  2. Runbook references are updated for Notification Service.
  3. The change can be linked from Jira remediation tickets and incident reviews.