🔔Notification Service
0 nodes · 0 edgesHint 1 — locked
Hint 2 — locked
Hint 3 — locked
🔔
Notification Service
● Beginner20–30 min
Problem
Build a notification service that other internal services can call to send email, push notifications, and SMS to users. Notifications must be delivered reliably even if downstream providers (SendGrid, FCM, Twilio) are temporarily unavailable. The system must scale to millions of notifications per day.
Functional Requirements
- Accept notification requests via an API (channel, recipient, message)
- Support email, push notifications, and SMS channels
- Retry failed deliveries with exponential back-off
- Track delivery status (pending, sent, failed)
- Allow priority lanes (transactional vs marketing)
Non-Functional
- 10M notifications per day across all channels
- Transactional notifications delivered within 5 seconds
- At-least-once delivery guarantee
- Isolated — one channel failure must not block others
🔔
Design your Notification Service
Drag components from the Brief panel → switch to Components tab
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
UML
15
Needs Work
Click a dimension to see what's missing. Score updates as you design.
Speed
RPS
Hit Play to start simulation00:00