Frontend System Design Mock Interview 2024
Вставка
- Опубліковано 23 тра 2024
- ------------------------------------------------------------------------------------------
👇🏼 HOW WE CAN HELP YOU
🤔 Find Your Technical Gaps With This FREE 10-Minute Technical Assessment
learn.theseniordev.com/techni...
🚀 Get Rid Of Impostor Syndrome And Fast-track To Senior Level
learn.theseniordev.com/free-tr...
------------------------------------------------------------------------------------------
I felt like this only began to touch on quite generic frontend system architecture at 17:00. I have not had FE System Design interviews that have asked me to build out the architecture of the entire system. Especially around things like deciding to add a CDN to better handle large loads. I *have* had generic "System Design" interviews do that, though.
Although the virtualized scrolling mention touches on performance, there was no discussion around state management, internationalization, accessibility, API design, and so on.
We are preparing a much more in depth part two :)
Really helpful! Thank you for making these videos 🙌🏻
You are welcome Anastasia!
Awesome content, very useful ❤
Thank you!
Great video guys, keep doing this kind of videos.
Thanks for the feedback @Ignacio!
Thank you for creating such informative videos .
Please make video on system design which includes about architectural patterns.Which pattern should be picked and why . Benefits and tradeoffs.
Thank you so much!
You're welcome! 🙏
quality content, this was very good
Thanks Cristobal! Glad you enjoyed it :)
Amazing job done here!
I'm wondering if you can create another session about interview questions related to SOLID principles and OOP principles. I got these questions a few days ago in an interview. Thank you!
Wishing you all the best!
We will add this to our backlog @Adi! Thanks for the suggestion
This video was good reason it covers more than frontend. But your title says Frontend System Design but most of the discussion was around backend stuff like load balancer, db, redis etc, which a frontend would never take these decisions. So its kind of mis-leading when you say frontend system design.
Ideally imo, frontend system design would talk about ui architecture, component decisions, data store, optimisation in frontend etc.
Hey @gokul, we are preparing a part two, that will be focused specifically on the client side system design - stay tunned!
Need lot more in depth ❤
Noted @madhanravi
Need more full Stack system design. Particularly for millions users. How we can handle million users on front end and back end. Please first explain it and then do it with code example.
yes, we are working on a video like that, stay tuned
It doesn't make sense to ask this question because no one designs for a million users from day one. Everything just evolves and scales
@StingSting844 It’s an interview question, so they are probably going to ask you to design based on a high number of users and requests because the company may already be at that scale.
Great discussion! But I don't get that why it isn't a good case for SSR. Can you please explain?
Hey Ankit, because the feed is very dynamic and SEO is not important for the feed section, SSR does not pay off
You can't render server side because all the fetches happen statefully, during load. You could hydrate skeleton components, however, so your users get fast-er initial load times.
🔍 Find your technical gaps with this Free Technical Assessment: www.theseniordev.com/free-technical-assessment
Question: How is "likes/comments - out of scope" in this context? Where they gona be stored? "Cloud"?
Hey there, we left it out of scope to keep things simple! Given the real-time aspect it is a bit more complex to design
If likes/comments were in scope, there'd be a strong case to use a relational database, right?