Frontend System Design Interview (Build Instagram)

------------------------------------------------------------------------------------------

👇🏼 HOW WE CAN HELP YOU

🤔 Find Your Technical Gaps With This FREE 10-Minute Technical Assessment

🚀 Get Rid Of Impostor Syndrome And Fast-track To Senior Level

------------------------------------------------------------------------------------------

[sujoysaha]

I felt the conversation leaned heavily towards backend system design, covering primarily backend challenges.

[lelandrb]

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.

[gokulkrishh]

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.

[rixis]

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.

[pranitapanigrahi]

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.

[anastasiastarostina]

Really helpful! Thank you for making these videos 🙌🏻

[זוהרנייגו]

One of the best demo design interview i have seen

[adibirta]

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!

[ignaciopulicedonatto]

Great video guys, keep doing this kind of videos.

[Its.implyfai]

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

[ankitdawra]

Great discussion! But I don't get that why it isn't a good case for SSR. Can you please explain?

[haniahani]

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.

[holycode]

is stickiness an important metric when designing the system? DAU / MAU

[mistahendrix]

How would the requirements change if this was mobile instead of web?

[pnk-owyl]

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".

[synchromatik]

Question: How is "likes/comments - out of scope" in this context? Where they gona be stored? "Cloud"?

[miladzai]

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.

[jasmineellis]

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.