Designing a notification system. #systemdesignseries

Your explanation in the video was spot on! I’ve also implemented the same concept while studying distributed systems. Check it out here:

Nice!

@TosinOlugbenga For a notification system relying on upstream providers, I think backoffs shouldn’t be purely exponential. Some jitter is needed otherwise your retries can run you into rate limits or worst case thundering herd hammering down your upstream provider. What do you think?

@TosinOlugbenga You are correct, I’ll answer this if the thundering herd question comes up. You know how open ended this interviews are.

Awesome explanation. I've implemented some of the concepts here in this job queue package I'm building -

Nice

Please can you use white boards when discussing design questions

😅😅😅😅… I’ll put that under advisement.

i should just follow you at this point

I'm currently building something like this, please can I get a feedback. I've documented everything

👏👏👏👏

The way you simplify and break down some stuff is top notch. I'd love if you made a video on load balancing systems. Especially consistent hashing. Interviewers tend to love those.

Thanks for this

I was thinking, why use 4 different messages queue why not pub sub ? The only reason I can think of here is for retries , so it would depend are notification important or they are not .

Nice @chinedu_10

Nice 🔥🔥 would say for that multiple queues it is a fanout exchange basically clone that one message to multiple queues that need that one message so pushing to that one exchange get’s fanned out to multiple queues

have you considered systems design mentoring?

😅

Great video

Thanks

Nice

love your videos but they’re usually too long