Meta system design interview: Design Instagram (with ex-Meta data engineer)
HTML-код
- Опубликовано: 2 июн 2024
- Watch an ex-Meta data engineer answer a typical Meta system design question: Design Instagram
Book a coaching session with Karthik: igotanoffer.com/en/coach/kart...
Chapters:
00:00 Intro
00:50 How would you design Instagram?
01:01 1. Clarifications and requirements
05:50 2. APIs
11:25 3. Metrics
22:27 4. Data Model
33:40 5. High-level design
41:25 6.1 Design storage
46:13 6.2 Design: upload/download
50:07 6.3 Design: newsfeed
57:02 6.4 Design: following
58:45 7. Bring it all together
1:01:22 Outro
About us:
IGotAnOffer is the leading career coaching marketplace ambitious professionals turn to for help at high-stakes moments in their career. Get a job, negotiate your salary, get a promotion, plan your next career steps - we've got you covered whenever you need us.
Come and find us: igotanoffer.com/
Get 1-to-1 coaching and ace your tech interviews: igotanoffer.com/en/interview-coaching/type/tech-interview
This one is pretty high-quality compared to previous mock system designs in the channel, surprisingly it only got 3k views so far. Thank you, keep up the good work.
Hey I know this guy. I haven't had much experience with having to do System Design interview questions as a Data Engineer. However, I still think that it can be highly beneficial to start prepping now just in case. Not every DE role requires System & API Design questions. My challenge may also be s.t. I don't have any real-world experience building APIs so I am unsure if that would diminish my ability to land role despite being able to pass the API design round.
thank you very useful
Glad it was helpful!
Thanks for the effort on this channel!
But I really didn't like either the design or the scheduling of the interviewee. His priorities of discussion was terrible and focused a lot on not-very fun and important parts of the design instead of timeline generation and celebrity issues for a system with 1B users!. Was not clear why we have an extra service right before the Kafka queue ( why not just directly go from LB to Kafka) and then the uploader reads from Kafka and uploads/updates the storages and many more other issues for a design like that.
He did good job in the timeslot he had, kafka client is custom client, LB can not connect directly to kafka)
5TB/day i.e. 5*365 = 1825TB = 1.8 PB/day correction required here
Yup thanks ! agreed 1.8 PB / year 👍