Menu

Design a Notification System: Queues, Retries and Fan-out
πŸ“°

Design a Notification System: Queues, Retries and Fan-out

DEV Community: backendΒ·ScaleDojoΒ·8 days ago
#Kz0XjUXO
#devtobackend#devto#dev#message#design
Reading 0:00
15s threshold

Design a notification system looks simple. Send an email, a push, an SMS. Done.

Then the interviewer asks: What if the email provider is down? What if a user gets the same push twice? What if you need to notify 5 million followers at once? That is where the real design starts.

This post walks through a clean answer to notification system design, step by step.

1. Clarify requirements first

Ask before you draw:

Which channels? Push, email, SMS, in-app.

Real-time or can it be delayed?

Do users have preferences (mute, quiet hours)?

Scale: notifications per day, peak bursts.

Non-functional goals: no lost notifications, no duplicates, low latency for urgent ones (OTP), and one slow channel must not block the others.

2.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.