Mimir

ACME-5010: Spike for Notification Service reliability improvement 10

jira
notification
ae86df1ff2f2

jira/acme-5010-notification-spike.md

ACME-5010: Spike for Notification Service reliability improvement 10

Date: 2025-07-31 Type: Spike Priority: P2 Service: Notification Service Owner: Engagement Platform GitHub References: GH-5010, GH-5011 API References: API-NOTIFICATION-01, API-NOTIFICATION-02, API-NOTIFICATION-03, API-NOTIFICATION-04

Business Context

Acme Commerce depends on the Notification Service to protect customer trust during high-volume shopping periods. This ticket captures engineering work needed after operational reviews found risk from partial deploy where only half of the pods received new configuration.

Scope

  • Review service contract behavior against API-NOTIFICATION-03.
  • Update dashboards and alerts owned by Engagement Platform.
  • Coordinate rollout with the teams that operate Authentication Service, Checkout Service, Billing Service, Inventory Service, and Notification Service.
  • Link implementation work to GitHub items GH-5010, GH-5011.

Definition of Done

  • Tests cover nominal, timeout, replay, and malformed payload scenarios.
  • Runbook steps are updated and validated in staging.
  • Incident review owners can cite this ticket as remediation evidence.