Design a Notification System

Every modern application, from social networks to banking apps, relies on notifications to keep users informed and engaged. When you receive a push notification about a friend's message, an email receipt for your purchase, or an SMS verification code, you're witnessing a sophisticated distributed system in action—one that must deliver billions of messages per day with remarkable reliability.

Notification systems appear deceptively simple on the surface. Send a message when something happens—how hard can that be? But beneath this simplicity lies extraordinary complexity: coordinating multiple delivery channels, respecting user preferences, handling failures gracefully, preventing abuse, and scaling to millions of concurrent users while maintaining sub-second delivery latency.

A notification system is a platform that enables applications to communicate with users through various channels in a timely, reliable, and personalized manner. Unlike direct request-response communication, notifications are asynchronous, event-driven messages that inform users about events, actions, or information they care about.

The Core Mission:

At its heart, a notification system must accomplish three fundamental objectives:

1. Deliver the right message — Content that is relevant, actionable, and valuable to the recipient
2. Through the right channel — The delivery method that best matches the urgency and nature of the message
3. At the right time — Respecting user preferences, time zones, and contextual appropriateness

Multi-Channel Requirement:

Modern notification systems must support multiple channels simultaneously because:

• Different messages require different channels (2FA codes via SMS, marketing via email)
• Users have varying preferences for how they want to be reached
• Redundancy ensures critical messages get delivered even if one channel fails
• Channel availability varies by geography, device, and user state (online vs offline)

This multi-channel nature introduces significant complexity. A single notification event might need to be routed to multiple channels, formatted differently for each, delivered with channel-specific retry logic, and tracked for engagement across all channels.

Before diving into architecture, we must precisely define what the notification system must do. Functional requirements describe the features and capabilities the system must provide.

Non-functional requirements define the quality attributes of the system—how well it performs its functions. For notification systems, these requirements are particularly demanding due to the high volume, real-time nature, and user-facing impact of the service.

Reliability Considerations:

Notification systems must handle a unique reliability challenge: external dependencies. Unlike purely internal systems, notifications depend on:

• Push Notification Gateways — Apple Push Notification Service (APNs), Firebase Cloud Messaging (FCM), Web Push Protocol
• Email Providers — SendGrid, Amazon SES, Mailgun, or self-hosted SMTP servers
• SMS Carriers — Twilio, Nexmo, or direct carrier connections

Each external provider has its own rate limits, failure modes, delivery semantics, and SLAs. The notification system must abstract these differences while providing consistent reliability guarantees to internal clients.

Understanding the scale of notification systems is crucial for making informed architectural decisions. Let's analyze the volume characteristics of a notification system serving a platform like Facebook, Twitter, or a major e-commerce site.

Traffic Patterns:

Notification traffic is highly variable and exhibits distinct patterns:

1. Diurnal Patterns — Traffic peaks during waking hours in major time zones, with valleys overnight. A global platform sees rolling peaks as different regions wake up.

2. Event-Driven Spikes — Breaking news, viral content, or major sports events can cause 10-100x normal traffic within seconds.

3. Scheduled Campaigns — Marketing email blasts at 9 AM can create massive synchronized load.

4. Cascade Effects — A viral post generates comments, which generate notifications, which generate more engagement—a positive feedback loop.

Infrastructure Implications:

These patterns require:

• Elastic scaling to handle sudden spikes
• Queue-based architecture to buffer traffic surges
• Rate limiting to protect downstream providers
• Geographic distribution to handle time zone shifts efficiently

Notification systems serve vastly different use cases across industries. Understanding these use cases helps prioritize features and make appropriate trade-offs during design.

Designing a notification system involves navigating numerous constraints and challenges that don't exist in simpler systems. Understanding these upfront prevents costly re-architecture later.

Compliance and Legal Constraints:

Notification systems must navigate a complex regulatory landscape:

• GDPR (Europe) — Right to erasure requires purging all notification history for a user. Consent must be explicit and withdrawable.
• CCPA (California) — Users can request access to all data, including notification history.
• CAN-SPAM (US) — Marketing emails must include unsubscribe links honored within 10 days.
• TCPA (US) — SMS requires prior express consent; violations can cost $500-$1,500 per message.
• PECR (UK) — Additional restrictions on electronic marketing.

These regulations affect data retention, consent management, and unsubscribe handling—all of which must be built into the system from the start.

A well-designed notification system must be measurable. Defining success metrics upfront ensures alignment between engineering decisions and business outcomes.

Let's consolidate everything we've covered into a clear requirements specification that will guide our architecture decisions in subsequent pages.

What's Next:

With requirements clearly defined, we'll now dive into the channels themselves. The next page explores Push, Email, SMS, and In-App delivery channels in detail—their protocols, providers, best practices, and failure modes. Understanding each channel's characteristics is essential for designing an effective multi-channel routing strategy.