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.β¦