Systems Design Interview Concepts (for software engineers / full-stack web)

Please "like" the video to support my technical content, and I will be happy to make more for you 👍 I'll do one for mobile systems design if we can hit 5,000 likes.

MongoDB is web scale

These tips are way too elementary and nowhere nearly enough to pass a faang system design interview.

You are awesome

Pure gold as always :) TechKing

cheers to any one who though his screen is shaking.

Thanks.

when the person you hate the most makes a great point

thank you

Thanks Sir its really very very helpful , In 10 mins you covered all important key points

Round-robin DNS is not a good idea for load balancing. DNS calls are often cached and you will end up locking users out if the web server they've cached goes down.

Aaaah. Before Tech lead became too proud.

Old Tech lead before his villain arc is actually pretty helpful

It was helpful to hear the concepts explained differently with a different perspective. This helped clarify some of my confusion. Thanks again!
Too bad we never ran into each other when we were at UCSD. :)

Transitions between topics is seamless, awesome!

OMG they are so useful!! thank you!

Cool bro, I was waiting for a joke there lol, but this was a good technical video

that was super helpful

You're going to be a good dad.

Good summary

I never had to decrease the playback speed of a video... yes.. decrease, till now lol

For anyone who may be confused, it's "sharding" not "sharting."

Thank you for this video! It was super concise, easy to understand, and overall a very good intro to a lot of these concepts.

The little guys in the drawings were cute

Incredibly helpful! Thank you!

Hi

Thanks for hosting valuable information. For embedded software/ firmware positions specifically
would system design rounds be centered around distributed systems/search engine/chat applications
sort of design questions? What would a typical senior engineer interview pattern look like and
how system design rounds will be different from other senior dev roles?
Thanks

I can not pass a single day without watching the videos of TechLead.

Speaks too fast. Lots of information, should speak slowly.

Damn, so that’s why he’s the techlead. 🐐

Good video. AWS S3 isn't a file system though.

Great quick watch video before a System Design interview.

Very high quality content in few min, which takes years to learn

1. Load-balancing @
2. Caching @
3. Database schema design @
4. Slave-master replications
5. Database sharding @
6. NoSQL @
7. API design @

I can't believe this video exists. This man will singlehandedly helped me and others land a job even 5-10 years from now. I have no experience about scalability because my projects have never needed that much, but now I can atleast understand some terminology that would help a lot in system design interviews.

Quite intense content, good

This is pure gold

"Brevity is the soul of wit", they say, this video by "the" Tech lead is case in point.

Really liked the content, hope i can afford this course one day 🙏🏻

Man....you speak fast. i had to slow down the video lol

How to drink coffee while preparing for a system design interview as a millionaire

Dude Database Locking is literally what takes down enterprises

Thank you! It's helpful. Do you have any tip for eng manager interviews?

To paraphrase: There are mainly 3 servers... the techniques to scale them are: Webservers (load balancing), Database servers (Caching, Indexing and Replications), Content Servers (Content Delivery Networks)

for web... Load Balancing - To improve Throughput, Latency and Scalability - NGINX for enterprise, dns load balancing for basic cfg
for caching db - Memcache, Redis, Cassandra.
for caching img/vid/web files - CDN (Distributed File System e.g. Amazon S3)
for db... Replication - Replicate data on multiple Slave DBs for "Read" only and Master for Read+Write
Problem: Simultaneous DB Writes; Solution: Sharding (Horizontal sharding - Data from 1 table is split and each portion is maintained in different/multiple machines)
NoSQL - Not Relational - Essentially key-value pairs - E.g. MongoDB, Amazon's Dynamo DB and FireBase' FireStore

Can we get more on systems designs...
It would be really helpful...

The BEST TechLead video I ever watched hands down, you see he didn’t mention a single second that he’s an ex-Google ex-Facebook whatever, nor talking about his wife.
Straight to the point, thank yoi for breaking this concept to us 😅

Wow explained it like a piece of cake ✔️

Nah.... Not up to the mark.. promotional video..... News reader style......