Designing a real-time notification platform
One Friday evening, five failures, and the platform that prevents them: the two halves (providers and a real-time tier), FERNS and the requirements, five classes of notification, why one queue makes an OTP 8 minutes late, the estimate where SMS is 5% of messages and about 89% of the bill, the seven pieces of the architecture, one payment traced from the Send API to Priya's screen, the five records, the channel trade-offs, and how LinkedIn, Uber and Slack split the same problem.
01 · Previously
W06 · DAY 01 · Designing a Real-Time Notification Platform
Week 6: real-time delivery.
Previously: Week 5 capstone
Previously, in the Week 6 preview, you met this week's problem: one platform that must reach 50 million people on every channel, and reach them in real time while they're online.
0:00 / 20:40