Notification system in LLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the primary purpose of a notification system in software architecture?

To deliver timely messages or alerts to users or systems about events or updates, ensuring they stay informed and can take necessary actions.

beginner

Name two common types of notifications in a notification system.

Push notifications (sent to devices or browsers) and email notifications (sent via email).

intermediate

Why is it important to decouple the notification sender from the notification processor?

Decoupling allows the system to handle high loads better, improves scalability, and makes maintenance easier by separating concerns.

intermediate

What role does a message queue play in a notification system?

It acts as a buffer to hold notification tasks, enabling asynchronous processing and smoothing out spikes in notification requests.

advanced

How can a notification system ensure reliability and avoid losing notifications?

By using persistent storage for messages, retry mechanisms for failed deliveries, and acknowledgments to confirm receipt.

Which component is best suited to handle spikes in notification requests?

A Database

B Message queue

C Load balancer

D User interface

Message queues buffer incoming requests and allow asynchronous processing, helping to handle spikes smoothly.

What is a common way to send push notifications to mobile devices?

A Using SMTP protocol

B Using FTP servers

C Using HTTP GET requests only

D Using Firebase Cloud Messaging (FCM)

Firebase Cloud Messaging is a widely used service to send push notifications to mobile devices.

Why should notification sending be asynchronous?

A To block the main application flow

B To avoid using databases

C To improve user experience by not delaying responses

D To reduce the number of notifications

Asynchronous sending prevents delays in the main application, improving responsiveness.

Which of the following is NOT a notification channel?

A Database indexing

B SMS

C Push notification

D Email

Database indexing is a data optimization technique, not a notification channel.

What is a key benefit of using a retry mechanism in notification delivery?

A To ensure notifications are eventually delivered despite temporary failures

B To send duplicate notifications

C To reduce system load

D To avoid using message queues

Retry mechanisms help deliver notifications even if initial attempts fail temporarily.

Explain the main components of a scalable notification system and how they interact.

Think about how messages flow from creation to delivery without blocking the main app.

Describe strategies to ensure reliability and fault tolerance in a notification system.

Consider what happens if a notification fails to send or the system crashes.

Practice

1. Which component in a notification system is responsible for generating events that trigger notifications?

easy

A. Delivery Channel

B. Notification Service

C. User Preferences Store

D. Event Producer

Solution

1. Step 1: Understand the role of event producers

   Event producers create or detect events that require notifying users, such as a new message or alert.

2. Step 2: Differentiate from other components

   Notification service processes events, delivery channels send notifications, and user preferences store user settings.

3. Final Answer:

   Event Producer -> Option D

4. Quick Check:

   Event source = Event Producer [OK]

Hint: Event creators are called producers in notification systems [OK]

Common Mistakes:

• Confusing notification service with event producer
• Thinking delivery channel generates events
• Assuming user preferences create events

2. Which of the following is the correct sequence of components for sending a notification after an event occurs?

easy

A. Delivery Channel -> Notification Service -> Event Producer

B. Event Producer -> Notification Service -> Delivery Channel

C. Notification Service -> Event Producer -> Delivery Channel

D. User Preferences Store -> Event Producer -> Delivery Channel

Solution

1. Step 1: Identify the logical flow of notification

   First, an event is generated by the event producer, then processed by the notification service, and finally sent via the delivery channel.

2. Step 2: Eliminate incorrect sequences

   Delivery channel cannot start the process; user preferences store is not part of the sending sequence.

3. Final Answer:

   Event Producer -> Notification Service -> Delivery Channel -> Option B

4. Quick Check:

   Event -> Process -> Send = A [OK]

Hint: Notifications flow from event to service to delivery [OK]

Common Mistakes:

• Reversing the order of components
• Including user preferences in the sending chain
• Confusing delivery channel as event source

3. Consider a notification system where users can choose email or SMS as delivery channels. If a user prefers both, what is the expected behavior when an event triggers a notification?

medium

A. Send notification via both email and SMS

B. Send notification via email only

C. Send notification via SMS only

D. Do not send any notification

Solution

1. Step 1: Understand user preference handling

   If a user selects multiple delivery channels, the system should send notifications through all preferred channels to ensure delivery.

2. Step 2: Confirm expected multi-channel delivery

   Sending via both email and SMS respects user choice and increases notification reach.

3. Final Answer:

   Send notification via both email and SMS -> Option A

4. Quick Check:

   Multiple preferences = multiple channels [OK]

Hint: Send notifications on all user-selected channels [OK]

Common Mistakes:

• Sending notification on only one channel
• Ignoring user preferences
• Not sending notification at all

4. A notification system uses a queue to handle event processing but notifications are delayed significantly. Which is the most likely cause?

medium

A. Queue is overloaded with too many events

B. User preferences are not stored

C. Delivery channel is sending notifications instantly

D. Event producer is generating too few events

Solution

1. Step 1: Analyze queue role in notification system

   Queue buffers events to handle load. If overloaded, it causes delays in processing notifications.

2. Step 2: Evaluate other options

   Missing user preferences or instant delivery does not cause delay; too few events would reduce load, not increase delay.

3. Final Answer:

   Queue is overloaded with too many events -> Option A

4. Quick Check:

   Queue overload = delay [OK]

Hint: Delays often mean queue overload, not missing data [OK]

Common Mistakes:

• Blaming delivery channel for delays
• Assuming missing preferences cause delay
• Thinking fewer events cause delays

5. You need to design a notification system that supports millions of users with personalized preferences and multiple delivery channels. Which design choice best ensures scalability and user customization?

hard

A. Use a centralized notification service with a single queue and fixed delivery channels

B. Store all user preferences in a local file on the notification server

C. Implement distributed notification services with sharded queues and dynamic delivery channel selection per user

D. Send notifications synchronously from event producers directly to users

Solution

1. Step 1: Consider scalability requirements

   Millions of users require distributed services and sharded queues to handle load without bottlenecks.

2. Step 2: Address user customization needs

   Dynamic delivery channel selection per user allows personalized notifications respecting preferences.

3. Step 3: Evaluate other options

   Centralized service and single queue create bottlenecks; synchronous sending blocks processing; local files do not scale or support dynamic preferences.

4. Final Answer:

   Implement distributed notification services with sharded queues and dynamic delivery channel selection per user -> Option C

5. Quick Check:

   Distributed + dynamic preferences = scalable & customizable [OK]

Hint: Distribute services and shard queues for scale and flexibility [OK]

Common Mistakes:

• Choosing centralized design causing bottlenecks
• Using synchronous sending blocking system
• Storing preferences in non-scalable local files