Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading the challenge…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
A company wants one internal service that every product team calls to notify customers — order updates, security alerts, reminders — by phone push, email or text message, depending on each customer's preferences. Teams fire requests in bursts of hundreds of thousands, for example when a sale starts, and the calling team must get an answer immediately rather than waiting for delivery. The outside email and text providers are slow and sometimes fail, so a failed send must be retried later without being lost, and nobody should ever receive the same notification twice. Preferences, such as a customer who has turned email off, change rarely but are checked on every send.
Every system design question opens with an account. Your design is scored the same way every time, with the reason behind each requirement, and your attempts are kept so you can see what you found hard.