Push notification integration in HLD - Architecture Diagram

System Overview - Push notification integration

This system sends push notifications to users' devices. It must handle many users, deliver messages quickly, and retry if delivery fails.

Architecture Diagram

User Devices
    |
    v
+----------------+
| Push Service   |
| (API Gateway)  |
+----------------+
    |
    v
+----------------+
| Notification   |
| Dispatcher     |
+----------------+
    |
    v
+----------------+       +----------------+
| Message Queue  |<----->| Retry Service  |
+----------------+       +----------------+
    |
    v
+----------------+
| Push Provider  |
| (APNs/FCM)     |
+----------------+

Components

User Devices

client

Receive push notifications

Push Service

api_gateway

Accept notification requests from apps

Notification Dispatcher

service

Process and send notifications to message queue

Message Queue

queue

Buffer notifications for delivery and retries

Retry Service

service

Handle failed deliveries and retry sending

Push Provider

external_service

Deliver notifications to user devices (e.g., APNs for iOS, FCM for Android)

Request Flow - 6 Hops

User Devices → Push Service

Push Service → Notification Dispatcher

Notification Dispatcher → Message Queue

Message Queue → Push Provider

Push Provider → Retry Service

Retry Service → Message Queue

Failure Scenario

Component Fails:Message Queue

Impact:Notifications cannot be buffered or retried, causing message loss or delivery delays

Mitigation:Use a replicated queue system with failover to ensure availability and durability

Architecture Quiz - 3 Questions

Which component buffers notifications to handle delivery retries?

A Push Service

B Message Queue

C Retry Service

D Notification Dispatcher

Design Principle

This design uses a message queue to decouple notification creation from delivery. It improves reliability by buffering messages and enabling retries. External push providers handle device delivery, while internal services manage request intake and failure handling.

Practice

1. What is the main purpose of integrating push notifications in a mobile app?

easy

A. To keep users updated even when the app is closed

B. To increase app size significantly

C. To slow down the app performance

D. To disable user interaction

Solution

1. Step 1: Understand push notification purpose

   Push notifications are messages sent to users to keep them informed or engaged.

2. Step 2: Identify correct purpose in options

   Only To keep users updated even when the app is closed correctly states that notifications keep users updated even when app is closed.

3. Final Answer:

   To keep users updated even when the app is closed -> Option A

4. Quick Check:

   Push notifications = keep users updated [OK]

Hint: Push notifications inform users outside the app [OK]

Common Mistakes:

• Thinking notifications increase app size
• Believing notifications slow app down
• Assuming notifications disable interaction

2. Which code snippet correctly requests user permission for push notifications in a mobile app?

easy

A. requestNotificationPermission();

B. enablePushNotifications();

C. askUserForNotificationPermission();

D. requestPermissionForNotifications();

Solution

1. Step 1: Identify standard permission request method

   Common method names include 'requestPermissionForNotifications' to ask user consent.

2. Step 2: Compare options for correct syntax

   requestPermissionForNotifications(); uses a clear, standard naming pattern for requesting permission.

3. Final Answer:

   requestPermissionForNotifications(); -> Option D

4. Quick Check:

   Permission request method = requestPermissionForNotifications() [OK]

Hint: Look for method names starting with 'requestPermission' [OK]

Common Mistakes:

• Using method names that don't request permission
• Confusing enabling notifications with requesting permission
• Using non-standard or undefined method names

3. Given this code snippet handling a push notification:

onNotificationReceived(notification) {
  if (notification.type === 'message') {
    showAlert(notification.title);
  }
}

What happens when a notification with type 'message' arrives?

medium

A. An alert with the notification title is shown

B. The notification is ignored

C. The app crashes due to missing handler

D. A log is printed but no alert

Solution

1. Step 1: Analyze the notification type check

   The code checks if notification.type equals 'message'.

2. Step 2: Understand the action on matching type

   If true, it calls showAlert with notification.title, displaying an alert.

3. Final Answer:

   An alert with the notification title is shown -> Option A

4. Quick Check:

   Type 'message' triggers alert display [OK]

Hint: Check condition and action inside notification handler [OK]

Common Mistakes:

• Assuming notification is ignored
• Thinking app crashes without error
• Confusing logging with alert display

4. Identify the error in this push notification handler code:

function handleNotification(notification) {
  if notification.isRead = false {
    displayNotification(notification);
  }
}

medium

A. Missing semicolon after function declaration

B. Using assignment '=' instead of comparison '==' in if condition

C. Incorrect function name 'handleNotification'

D. Notification object missing required fields

Solution

1. Step 1: Check the if condition syntax

   The condition uses '=' which assigns value instead of comparing.

2. Step 2: Identify correct comparison operator

   It should use '==' or '===' to compare values, not '='.

3. Final Answer:

   Using assignment '=' instead of comparison '==' in if condition -> Option B

4. Quick Check:

   Use '==' for comparison, not '=' [OK]

Hint: Remember '=' assigns, '==' compares in conditions [OK]

Common Mistakes:

• Confusing assignment and comparison operators
• Ignoring syntax errors in if statements
• Assuming function name causes error

5. You want to send a push notification only if the user has granted permission and the app is in background. Which logic correctly implements this?

hard

A. if (userPermissionGranted && appState !== 'background') { sendPushNotification(); }

B. if (userPermissionGranted || appState === 'background') { sendPushNotification(); }

C. if (userPermissionGranted && appState === 'background') { sendPushNotification(); }

D. if (!userPermissionGranted && appState === 'background') { sendPushNotification(); }

Solution

1. Step 1: Understand conditions for sending notification

   Notification should send only if permission is granted AND app is in background.

2. Step 2: Evaluate logical operators in options

   if (userPermissionGranted && appState === 'background') { sendPushNotification(); } uses '&&' (AND) correctly to check both conditions.

3. Final Answer:

   if (userPermissionGranted && appState === 'background') { sendPushNotification(); } -> Option C

4. Quick Check:

   Use AND (&&) to require both conditions [OK]

Hint: Use AND (&&) to combine required conditions [OK]

Common Mistakes:

• Using OR (||) instead of AND (&&)
• Negating permission incorrectly
• Checking wrong app state