Mimir

← Back to documents

ACME-5020: Spike for Notification Service reliability improvement 20

jira
notification
dd81b19f32ef

jira/acme-5020-notification-spike.md

ACME-5020: Spike for Notification Service reliability improvement 20

Date: 2025-11-18 Type: Spike Priority: P0 Service: Notification Service Owner: Engagement Platform GitHub References: GH-5020, GH-5001 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-01.
  • 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-5020, GH-5001.

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.