Push notifications are often measured at the wrong boundary.
A successful provider response confirms acceptance for processing—not device receipt, display, or user interaction.
Reliable architecture treats push as an expiring, duplicate-prone signal, while the authenticated backend remains the source of truth.
What Reliability Requires
- Transactional outbox processing
- Installation-aware token management
- Bounded, expiration-aware retries
- Event identifiers and version checks
- Deduplication and idempotent processing
- Client reconciliation with authoritative APIs
Push payloads should carry opaque references instead of sensitive business data. When opened, the application must authenticate the user, authorize access, and retrieve the latest state.
Collapse identifiers can reduce stale pending messages, but they do not replace deduplication or version validation.
The Practical Goal
Exactly-once presentation cannot be established across provider, operating-system, and application boundaries.
The practical goal is to preserve correctness when notifications arrive late, more than once, out of order, or not at all.
Top comments (0)