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.
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.
A frontend system design interview is not going to require you to go into depth on what's happening on the server, you can treat it as a black box. You should really take frontend out of the title of this video as asking questions about load, peak hours, scaling etc would much better suit a backend role, perhaps "Fullstack system design mock interview" would be better. Frontend is going to care more about how your UI handles data, how the UI communicates data between the client-store and the server, interactions and what APIs you'll need and the data they might use.
that might be true, but you don't get to choose how companies interview you, some companies will keep it 100% FE others will go into fullstack topics even in a FE interview, which is why the safe bet is to be prepared for both
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.
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!
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.
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.
@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.
I don't agree withsome aspects of this process. This was about Frontend, you don't have to include databases and image blob storage solutions. That's BE headache, not FE.
Why at the video you focussed more on the big picture like how the Frontend communicates with backend, and about data bases, CDN, Load balancers and so on? I supposed this is more about the backend system interviews? Comparing your other video "Frontend System Design Interview (Build Google Search)" with this one, it messes my mind a little bit about what is "Frontend System Design".
There's no reason why pagination or interactivity make this a bad candidate for SSR. All this can be achieved with server actions. Pre-rendering is just one performance benefit you get from SSR.
pagination and interactivity increase complexity, SSR is already complex by itself. Pre-rendering is a performance and SEO benefit, but it comes at a cost, that is, more complexity.
@@therealseniordev As I said, prerendering is just one performance benefit. Security is another aspect. I think it comes to seem less complicated once developers acclimatize to it.
I felt the conversation leaned heavily towards backend system design, covering primarily backend challenges.
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 :)
@@therealseniordev still preparing?
@@therealseniordev this part two must have the same depth as the mariana trench since that comment was 4 months ago lol
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!
A frontend system design interview is not going to require you to go into depth on what's happening on the server, you can treat it as a black box. You should really take frontend out of the title of this video as asking questions about load, peak hours, scaling etc would much better suit a backend role, perhaps "Fullstack system design mock interview" would be better.
Frontend is going to care more about how your UI handles data, how the UI communicates data between the client-store and the server, interactions and what APIs you'll need and the data they might use.
that might be true, but you don't get to choose how companies interview you, some companies will keep it 100% FE others will go into fullstack topics even in a FE interview, which is why the safe bet is to be prepared for both
I totally agree to @rixis2940 . This video is misleading. This is not a front end system design . it is misleading .
I am agree with you. This video is about full stack system design..
This the best UA-cam channel
Really helpful! Thank you for making these videos 🙌🏻
You are welcome Anastasia!
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.
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
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.
Great video guys, keep doing this kind of videos.
Thanks for the feedback @Ignacio!
How would the requirements change if this was mobile instead of web?
One of the best demo design interview i have seen
is stickiness an important metric when designing the system? DAU / MAU
Awesome content, very useful ❤
Thank you!
quality content, this was very good
Thanks Cristobal! Glad you enjoyed it :)
It's more like a FullStack / near Backend Design system rather than focusing on real frontend chalenges in this type of apps.
But very good content
Thank you so much!
You're welcome! 🙏
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.
Bogdan was not bogged down 🤣
I don't agree withsome aspects of this process. This was about Frontend, you don't have to include databases and image blob storage solutions. That's BE headache, not FE.
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?
Need lot more in depth ❤
Noted @madhanravi
Why at the video you focussed more on the big picture like how the Frontend communicates with backend, and about data bases, CDN, Load balancers and so on? I supposed this is more about the backend system interviews?
Comparing your other video "Frontend System Design Interview (Build Google Search)" with this one, it messes my mind a little bit about what is "Frontend System Design".
There's no reason why pagination or interactivity make this a bad candidate for SSR. All this can be achieved with server actions. Pre-rendering is just one performance benefit you get from SSR.
pagination and interactivity increase complexity, SSR is already complex by itself. Pre-rendering is a performance and SEO benefit, but it comes at a cost, that is, more complexity.
@@therealseniordev As I said, prerendering is just one performance benefit. Security is another aspect. I think it comes to seem less complicated once developers acclimatize to it.
🔍 Find your technical gaps with this Free Technical Assessment: www.theseniordev.com/free-technical-assessment