Claim Ownership
System Design
Subscribed: 239Played: 1,424
Subscribe
© 2021 System Design
Description
Software Engineers Wes Moncrief and Kevin Li discuss aspects of the system design interview, as well as related topics in designing large and interesting software architectures. If you're new here, I'd suggest starting with the episode "Facebook Timeline Interview". I'll also note that our first few episodes had lower quality audio than our subsequent episodes.We'd love to hear any listener feedback - email us at thesystemdesignpodcast@gmail.com
6 Episodes
Reverse
Top Podcasts
The Best New Comedy Podcast Right Now – June 2024The Best News Podcast Right Now – June 2024The Best New Business Podcast Right Now – June 2024The Best New Sports Podcast Right Now – June 2024The Best New True Crime Podcast Right Now – June 2024The Best New Joe Rogan Experience Podcast Right Now – June 20The Best New Dan Bongino Show Podcast Right Now – June 20The Best New Mark Levin Podcast – June 2024
Question: can something like Kafka take care of ALL the requirements for this use case? - it can handle large volume of data - it is resilient and can handle failures - each user could be a subscriber and when they login they just pull the unread statuses in their queue - each user's queue can handle chronology as well - for the celebrity case, it is a matter of heavy writes but eventually the message queue will get around to it Let me know your thoughts!
All that time during the discussion about postStatus() I kept thinking "message queue, message queue" and eventually Wes brought it up :) This is my first time tuning into this podcast and was a good listen. I'll be back. Good luck!