5:30 years and years of watching UA-cam videos and this has to be the most compelling way of asking for a sub yet, I would've subscribed had I not been subscribed already.
System design concepts explained in the video 👇 1. Vertical scaling - refers to increasing the resources (such as CPU, memory, or storage) of a single machine to improve its performance or handle higher workloads. 2. Horizontal scaling -adding more servers to a system to distribute the workload and increase overall capacity and performance. 3. Load balancer - A load balancer is a network device or software that evenly distributes incoming network traffic across multiple servers or resources to optimize performance and ensure high availability. 4. Content delivery networks - Content Delivery Networks (CDNs) are distributed networks of servers located geographically closer to end users, designed to deliver web content efficiently by caching and serving it from nearby locations 5. Caching - Caching is the process of storing frequently accessed data or content in a temporary storage location (cache) to improve retrieval speed and reduce the need for repeated requests 6. Internet Protocol Address - An IP address is a unique numerical label assigned to each device connected to a computer network 7. TCP - TCP (Transmission Control Protocol) is a communication protocol that ensures reliable, connection-oriented transmission of data by dividing it into smaller packets, numbering them, and reassembling them at the receiving end. 8. DNS - DNS (Domain Name System) is a decentralized naming system that translates human-readable domain names into IP addresses 9. HTTP - HTTP (Hypertext Transfer Protocol) is a protocol that governs the communication between web browsers and servers, allowing for the retrieval and transfer of web pages and resources over the internet. 10. REST - REST (Representational State Transfer) is an approach to designing web services that uses standard HTTP methods and URLs to facilitate communication between clients and servers. 11. GraphQL - GraphQL is a query language for APIs that provides a flexible and efficient way for clients to request and retrieve data from servers by allowing them to specify exactly what data they need. Using single query it can fetch multiple resources without overfetching as well. 12. gRPC - gRPC (Google Remote Procedure Call) is an open-source framework that enables efficient communication and interoperation between services by defining the interface and data contracts using Protocol Buffers and facilitating bi-directional streaming and error handling. 13. web sockets - WebSockets is a communication protocol that provides full-duplex, real-time, and bidirectional communication between a client and a server over a single, long-lived connection.WebSockets can be used in applications such as chat systems or real-time collaboration tools, where instant and continuous data exchange between clients and servers is required. 14. SQL - SQL (Structured Query Language) is a programming language used for managing and manipulating relational databases, allowing users to perform tasks such as querying data, defining database structure, and modifying data records. SQL is considered to use when fast retrieval of data is needed 15. ACID compliance - ACID (Atomicity, Consistency, Isolation, Durability) compliance is a set of properties that ensure reliability and integrity in database transactions, guaranteeing that they are executed reliably, consistently, and without interference. 16. NoSQL databases - NoSQL (Not Only SQL) databases are a class of databases that provide flexible, schema-less data models and horizontal scalability, making them suitable for handling large volumes of unstructured or semi-structured data. 17. Sharding - Sharding is a technique in database management where data is horizontally divided and distributed across multiple servers or nodes to improve performance, scalability, and load balancing. 18. Replication - Replication is the process of creating and maintaining identical copies of data across multiple servers or nodes, providing redundancy, fault tolerance, and improved data availability in distributed systems. 19. CAP thoerem - The CAP theorem states that in a distributed system, it is impossible to simultaneously guarantee consistency, availability, and partition tolerance, and therefore, trade-offs must be made between these three properties. 20. Message Queues - Kind of like databases because they have durable storage. They can be replicated for redunduncy or sharded for scalability. This can be used in task distribution and workload decoupling.
Scaling- (because getting more users) Vertical scaling (add resources) - Increasing CPU,RAM Horizontal scaling (add replica) - Increasing number of machines - scale infinitely, Redundancy, Fault tolerance, don't need good machines load balancer (server known as reverse proxy) {directs incoming requests to the apporiate server using algorithms like Round Robin(balance traffic by cycling through pool of servers) Hashing( hashing incoming request ID) } Static content- Content Delivery Networks CDN (network of servers located all over the world) (copying files from origin server to CDN servers done by push or pull basis) Cashing - storing frequently accessed data to RAM IP - Internet Protocol Address Internet protocol suite (IP , TCP, UDP) DNS Domain name system - buy from DNS registrar , create DNS A record (IP address of my server) Application layer protocol - HTTP Hypertext Transfer Protocol (client server model){client initiates a request which includes 1.Request Header(Address of destination and client, metadata), 2.Request Body} API Paradigms (REST API, GraphQL, gRPC) REST Representational State Transfer (standardization around HTTP API making them Stateless and following Consisting Guidelines){successful request should include 200 OK code in its response header, bad req from client would return a 400 Bad Request code, Issue with server 500 Internal server error level code} GraphQL(single request aka query)(fetch multiple resources with single request, no over fetching) gRPC (RPC framework){server to server communication} gRCP web - Protocol Buffers(data is serialized in binary format {storage efficient}) - performance improvement compared to JSON (used by REST API)(human readable) web sockets - Bidirectional Communication SQL (Relational Database Management System like MySQL, PostgreSQL){Efficient Storage using data structures like B-Trees, Fast & Power Retrieval of data using SQL(Structured Query Language) queries since data is organized into rows and tables}(RDMS is ACID compliance(Atomicity{Every transcation is All or Nothing}, Consistency{foreing key and other constraints will always be enforced}, Isolation{different concurrent transcations wont interfere with each other}, Durability{data is stored on disk})) NoSQL(Non relational databases)(No consistency){consistency makes DBs harder to scale} (NO enforcing of foreign key constraints){break up DB and scale horizontally (sharding)} DynamoDB(key-value stores), MongoDB(Document Stores), neo4j(graph DBs) sharding done by shard key (range based sharding)(like ID of person) Replication-(read only copies) (Leader follower Replication){ (every write would be sent to leader who sends them to followers, every read can go to leader or follower) Leader-->(replication)-->follower} - (leader leader replication)Replica for every region - CAP theorem (to keep replicain sync)
Message Queues (System receiving more data than it can process) durable storage and can be replicated for redundancy or sharded for scalability (Replication and sharding){ (read/write)Leader-->(replication)-->follower(read)}
Oh. My. Gosh. This is THE most concise video about Systems design I’ve seen. All this fragmented things I’ve heard finally make sense together. Thank you 🙏
The best part is that I am already familiar with most of the concepts mentioned in the video. Still, I didn't realize it fell under the 'System Design' category since I am a self-taught backend developer.
Interesting. This just further proves that frontend and backend really do have a distinct divide. Client side and server side. Client side definitely focusing more on human interaction, server side focusing more on the "motor/engine" of an app.
@@joaquin67 Yea. I had it put to me perfectly by a senior on my team. Backend developers are really just data plumbers. We build all the underground plumbing for data to be moved around. Front end developers build the fancy sinks, toilets, showers, etc... that get the data from the plumbing.
@@amcmillion3 I always love hearing the house analogy further improved as both are equally important. For example, I wish I had more outlets in my apartment that was built in the 80s, and more cabinets for things. Likewise, I wish the plumbing in my 2nd restroom didn't have the hot/cold water temperatures reversed. Backend is the bridge between data and frontend, frontend provides interaction between backend and human. Unfortunately, the human is the only level in the stack that can't always be debugged lol
The elegance of his explanations is greatly overpowered by the hilarity of reading "range-based sharding." I thought sharding was bad enough when kept local
Hey, it was a good and interesting video. Thanks. Writing summary for my understanding. 1. Horizontal scaling is better 2. Load balancers are used to choose which server to interact with 3. CDN are placed across the world, they help in faster delivery of static data. 4. Rest API - standardization of api request 5. Graphql - Ask only the data that required 6. Storage - Relational(Sql), Non relational (mongo) 7. Caching, message queues - Redis, Kafka
CS590 Software Architecture summarized in 10 mins, awesome...this was definitely the most bulky course and you did way better than my professor in explaining
Amazing video! I hate how slow so many videos are and how much fluff they contain. You manage to explain these concepts in SUCH a simple way, which is a truly valuable and rare skill. Also +1 for the 5:29 subscribe button use case.
NoSQL is older than relational databases. All DBMSes were NoSQL prior to that Codd paper. All the flavours existed back then, in the late 60s - early 70s - document, hierarchical, graph-based.
Man I bought your lifetime subscription and I can say you have a talent to explain complex concepts in a simple language. You should expand your course to more areas - for example Cloud services (AWS, GCP, Azure...) - there are tons of content topics there and there are no content for those topics on youtube in terms of explaining as good as yours. You should do it bro!
OMG tha was the most direct and simple way to explain a lot of important concepts! Every dev should watch this to understand more about the macro dev world
Goes to show u really understand the concept when u can explain all the terms so well and easy to understand, all while making connections to each feature! 👍🏼
oh my god, i'm halfway through and i just had to stop watching and come here to comments to tell how much i love the video. the way it is structured and how easily and smoothly it takes us from concept to concept, never breaking the flow is just amazing. very well done! thank you SO SO MUCH for putting it out here!
Should have mentioned queues back when you introduced horizontal scaling since you need it there and people would understand a fundamental use case more clearly.
Great job, I like how you balance between conciseness and covering just enough details so that people can further learn it if they are interested in a concept
Very Useful content, I loved the Design pattern video also. Had an interview on Friday, They asked about the strategy pattern, I told them how to Make FilterStrategy. 🤣 The round was was supposed to be 1 hour long but ended in half hour. I answered almost all questions. But there is no response from them.
@@spooder5022 Hi, I got the response and cleared all rounds, there was a round with VP after that. The HR is delaying the offer tho, He said he will give the offer last Monday. I called again and again. No response. Meanwhile I got an offer from an Ad Tech company. The process was very smooth interactive interviews. Its giving 30% hike. The above one is a Data Science AI company. I am very confused should I pressurize the other company for offer or go with ad tech.
Nice video, just one complaint. Buying domain is from a Domain Registrar, and while they can host your DNS for your domain, that isn't a requirement. For example, our customers have different registrars, but the DNS servers are with the hosting provider that we use, since they have a nice integration for adding their servers to their DNS records, without the chance of mistyping the IP address. And some of the hosting providers give you a much easier to use interface, than some of the registrars. I have over 25 years of experience with DNS servers, and initially, I had to hand edit the records in text files, so I really enjoy the interface provided by some of the hosting providers.
5:09 to be more precise, the request includes 3 parts: request line, request header and request body. Same for response, it includes 3 parts: status line, response header and response body
I really loved all the concepts. I'm a front-end heavy full stack developer wanting to upskill in the backend department. These pointers are really helpful. Could anyone point me in the right direction to learn more advanced topics on database designs and it's efficiency?
bro no wonder the name of ur channel is neet because the video i've just watched is so neat really. this is the first time visiting ur channel and i hope i find many more amazing video like this one. Thank u
so far the only tech youtuber I have followed whom sticks to tech topics rather than to just film “how to crack the leetcode in 3 months” or “what a day looks like as a sde”😂
Bro this video is so much priceless ! It is one of the best or The best I have ever watched ! I learned so much on some specific points. This one should be given to any Junior learner or even Experience dev as well. So glad this one came on my feed. Amazing work Sir !!
really cool the way he intertwined these concepts. Also this is the first time ive heard database replication referred to as "leader adn follower". Come on now lol its master and slave instances.
My experience with AWS interviews was that no matter how much system design you practice, in the end they're gonna want previous experience with cloud and backend, not just theory. Unless you're applying for a junior role.
@@garrettfiorito4482 how do you get experience to intermediate if you can’t get experience as a junior? Do you just look for unpaid internships? Sounds unproductive, prob need to know someone who already works there for connections.
5:30 years and years of watching UA-cam videos and this has to be the most compelling way of asking for a sub yet, I would've subscribed had I not been subscribed already.
He made a mistake. He showed the response body instead of the request body (payload) hence I'm not subscribing 😁
I love how the topics are connected to one another in a simple and neat way.
dont you mean "neet" way?
can't believe he missed it
In a neet way!
System design concepts explained in the video 👇
1. Vertical scaling - refers to increasing the resources (such as CPU, memory, or storage) of a single machine to improve its performance or handle higher workloads.
2. Horizontal scaling -adding more servers to a system to distribute the workload and increase overall capacity and performance.
3. Load balancer - A load balancer is a network device or software that evenly distributes incoming network traffic across multiple servers or resources to optimize performance and ensure high availability.
4. Content delivery networks - Content Delivery Networks (CDNs) are distributed networks of servers located geographically closer to end users, designed to deliver web content efficiently by caching and serving it from nearby locations
5. Caching - Caching is the process of storing frequently accessed data or content in a temporary storage location (cache) to improve retrieval speed and reduce the need for repeated requests
6. Internet Protocol Address - An IP address is a unique numerical label assigned to each device connected to a computer network
7. TCP - TCP (Transmission Control Protocol) is a communication protocol that ensures reliable, connection-oriented transmission of data by dividing it into smaller packets, numbering them, and reassembling them at the receiving end.
8. DNS - DNS (Domain Name System) is a decentralized naming system that translates human-readable domain names into IP addresses
9. HTTP - HTTP (Hypertext Transfer Protocol) is a protocol that governs the communication between web browsers and servers, allowing for the retrieval and transfer of web pages and resources over the internet.
10. REST - REST (Representational State Transfer) is an approach to designing web services that uses standard HTTP methods and URLs to facilitate communication between clients and servers.
11. GraphQL - GraphQL is a query language for APIs that provides a flexible and efficient way for clients to request and retrieve data from servers by allowing them to specify exactly what data they need. Using single query it can fetch multiple resources without overfetching as well.
12. gRPC - gRPC (Google Remote Procedure Call) is an open-source framework that enables efficient communication and interoperation between services by defining the interface and data contracts using Protocol Buffers and facilitating bi-directional streaming and error handling.
13. web sockets - WebSockets is a communication protocol that provides full-duplex, real-time, and bidirectional communication between a client and a server over a single, long-lived connection.WebSockets can be used in applications such as chat systems or real-time collaboration tools, where instant and continuous data exchange between clients and servers is required.
14. SQL - SQL (Structured Query Language) is a programming language used for managing and manipulating relational databases, allowing users to perform tasks such as querying data, defining database structure, and modifying data records. SQL is considered to use when fast retrieval of data is needed
15. ACID compliance - ACID (Atomicity, Consistency, Isolation, Durability) compliance is a set of properties that ensure reliability and integrity in database transactions, guaranteeing that they are executed reliably, consistently, and without interference.
16. NoSQL databases - NoSQL (Not Only SQL) databases are a class of databases that provide flexible, schema-less data models and horizontal scalability, making them suitable for handling large volumes of unstructured or semi-structured data.
17. Sharding - Sharding is a technique in database management where data is horizontally divided and distributed across multiple servers or nodes to improve performance, scalability, and load balancing.
18. Replication - Replication is the process of creating and maintaining identical copies of data across multiple servers or nodes, providing redundancy, fault tolerance, and improved data availability in distributed systems.
19. CAP thoerem - The CAP theorem states that in a distributed system, it is impossible to simultaneously guarantee consistency, availability, and partition tolerance, and therefore, trade-offs must be made between these three properties.
20. Message Queues - Kind of like databases because they have durable storage. They can be replicated for redunduncy or sharded for scalability. This can be used in task distribution and workload decoupling.
Thanks Brother
Thanks man! God bless you
Thanks man :)
You fucking legend. I was going to make some notes. You saved me time. Cheers
HOLY BASED
Scaling- (because getting more users)
Vertical scaling (add resources) - Increasing CPU,RAM
Horizontal scaling (add replica) - Increasing number of machines
- scale infinitely, Redundancy, Fault tolerance, don't need good machines
load balancer (server known as reverse proxy) {directs incoming requests to the apporiate server using algorithms like Round Robin(balance traffic by cycling through pool of servers) Hashing( hashing incoming request ID) }
Static content- Content Delivery Networks CDN (network of servers located all over the world) (copying files from origin server to CDN servers done by push or pull basis)
Cashing - storing frequently accessed data to RAM
IP - Internet Protocol Address Internet protocol suite (IP , TCP, UDP)
DNS Domain name system - buy from DNS registrar , create DNS A record (IP address of my server)
Application layer protocol - HTTP Hypertext Transfer Protocol (client server model){client initiates a request which includes 1.Request Header(Address of destination and client, metadata), 2.Request Body}
API Paradigms (REST API, GraphQL, gRPC)
REST Representational State Transfer (standardization around HTTP API making them Stateless and following Consisting Guidelines){successful request should include 200 OK code in its response header, bad req from client would return a 400 Bad Request code, Issue with server 500 Internal server error level code}
GraphQL(single request aka query)(fetch multiple resources with single request, no over fetching)
gRPC (RPC framework){server to server communication}
gRCP web - Protocol Buffers(data is serialized in binary format {storage efficient}) - performance improvement compared to JSON (used by REST API)(human readable)
web sockets - Bidirectional Communication
SQL (Relational Database Management System like MySQL, PostgreSQL){Efficient Storage using data structures like B-Trees, Fast & Power Retrieval of data using SQL(Structured Query Language) queries since data is organized into rows and tables}(RDMS is ACID compliance(Atomicity{Every transcation is All or Nothing}, Consistency{foreing key and other constraints will always be enforced}, Isolation{different concurrent transcations wont interfere with each other}, Durability{data is stored on disk}))
NoSQL(Non relational databases)(No consistency){consistency makes DBs harder to scale} (NO enforcing of foreign key constraints){break up DB and scale horizontally (sharding)} DynamoDB(key-value stores), MongoDB(Document Stores), neo4j(graph DBs)
sharding done by shard key (range based sharding)(like ID of person)
Replication-(read only copies) (Leader follower Replication){ (every write would be sent to leader who sends them to followers, every read can go to leader or follower) Leader-->(replication)-->follower} -
(leader leader replication)Replica for every region - CAP theorem (to keep replicain sync)
Message Queues (System receiving more data than it can process) durable storage and can be replicated for redundancy or sharded for scalability
(Replication and sharding){ (read/write)Leader-->(replication)-->follower(read)}
Oh. My. Gosh. This is THE most concise video about Systems design I’ve seen. All this fragmented things I’ve heard finally make sense together. Thank you 🙏
The best part is that I am already familiar with most of the concepts mentioned in the video. Still, I didn't realize it fell under the 'System Design' category since I am a self-taught backend developer.
Interesting. This just further proves that frontend and backend really do have a distinct divide. Client side and server side. Client side definitely focusing more on human interaction, server side focusing more on the "motor/engine" of an app.
@@joaquin67 Yea. I had it put to me perfectly by a senior on my team. Backend developers are really just data plumbers. We build all the underground plumbing for data to be moved around. Front end developers build the fancy sinks, toilets, showers, etc... that get the data from the plumbing.
@@amcmillion3 I always love hearing the house analogy further improved as both are equally important. For example, I wish I had more outlets in my apartment that was built in the 80s, and more cabinets for things. Likewise, I wish the plumbing in my 2nd restroom didn't have the hot/cold water temperatures reversed. Backend is the bridge between data and frontend, frontend provides interaction between backend and human. Unfortunately, the human is the only level in the stack that can't always be debugged lol
The elegance of his explanations is greatly overpowered by the hilarity of reading "range-based sharding." I thought sharding was bad enough when kept local
Hey, it was a good and interesting video. Thanks.
Writing summary for my understanding.
1. Horizontal scaling is better
2. Load balancers are used to choose which server to interact with
3. CDN are placed across the world, they help in faster delivery of static data.
4. Rest API - standardization of api request
5. Graphql - Ask only the data that required
6. Storage - Relational(Sql), Non relational (mongo)
7. Caching, message queues - Redis, Kafka
This is one of the highest quality, most dense and seamless educational videos I've ever seen. Really smart, neetcode!
CS590 Software Architecture summarized in 10 mins, awesome...this was definitely the most bulky course and you did way better than my professor in explaining
Bowing down to this incredibly well made content. Thank you so much!
Well done! Very digestible explanation with great motion graphics to help illustrate!
This is so well put together. So clear, concise and great graphics.
Amazing video! I hate how slow so many videos are and how much fluff they contain. You manage to explain these concepts in SUCH a simple way, which is a truly valuable and rare skill. Also +1 for the 5:29 subscribe button use case.
Thank you for your hard work!
@@sunset7456 thats much more than 5$ bro 4000/80 is 50 dollars
Bro just dropped 4k 💀
@@Nischal.shetty02 no bro actuallybri dropped class 4..😂😂
bhai....kitne ki package lagni hoti hai....aise 4k donate karne ke liye???
NoSQL is older than relational databases. All DBMSes were NoSQL prior to that Codd paper. All the flavours existed back then, in the late 60s - early 70s - document, hierarchical, graph-based.
Really? Wow I wouldn't have thought so!
Man I bought your lifetime subscription and I can say you have a talent to explain complex concepts in a simple language. You should expand your course to more areas - for example Cloud services (AWS, GCP, Azure...) - there are tons of content topics there and there are no content for those topics on youtube in terms of explaining as good as yours. You should do it bro!
OMG tha was the most direct and simple way to explain a lot of important concepts! Every dev should watch this to understand more about the macro dev world
The most creative way to ask people to subscribe! If I could, I would have subscribed 10 more times. Absolute genius!
Goes to show u really understand the concept when u can explain all the terms so well and easy to understand, all while making connections to each feature! 👍🏼
I loved the graphics and the way you tied everything together in one place.
Crisp & clear content. You were able to cover most of the important topics in just 10 min. Nice keep up the good work.
oh my god, i'm halfway through and i just had to stop watching and come here to comments to tell how much i love the video. the way it is structured and how easily and smoothly it takes us from concept to concept, never breaking the flow is just amazing. very well done! thank you SO SO MUCH for putting it out here!
I really like the way you pronounce ser-v-er. It slows down a bit which magically bring more order into the understanding.
I like how the topics are connected to one another in a simple way. Happy teacher's day🙌
i can see my years learning web in 10 minutes. very well made content and great explanation.
Should have mentioned queues back when you introduced horizontal scaling since you need it there and people would understand a fundamental use case more clearly.
Great job, I like how you balance between conciseness and covering just enough details so that people can further learn it if they are interested in a concept
Very Useful content, I loved the Design pattern video also.
Had an interview on Friday, They asked about the strategy pattern, I told them how to Make FilterStrategy. 🤣 The round was was supposed to be 1 hour long but ended in half hour. I answered almost all questions. But there is no response from them.
Where did you get filter strategy video in this channel?
@@sunithaarganurkar7486 Search for neetcode design pattern, watch the video, he will explain with code. Pause the video to have better understanding.
how did it go?
did you hear back?
@@spooder5022
Hi, I got the response and cleared all rounds, there was a round with VP after that. The HR is delaying the offer tho, He said he will give the offer last Monday. I called again and again. No response.
Meanwhile I got an offer from an Ad Tech company. The process was very smooth interactive interviews. Its giving 30% hike.
The above one is a Data Science AI company.
I am very confused should I pressurize the other company for offer or go with ad tech.
omg bro this is so much better than all other vids about system interview that I have seen
This is truly awesome. A great recap/overview!
This is the best short video I have ever seen about the system design. Keep up the good work.
Explained in simple and graphical way., that’s awesome!!
Best ever! Compact and interesting intro to system design concepts!!! Excellent!
So much information in 11 minutes. Thank you for making it happen. Very helpful.
Awesome summary, I was actually looking for it.
05:32 It was the most intuitive way of getting subscribed.
Most valuable 10 mins was spend! No second was wasted. kudo to you!
Great video, this is exactly what i was looking for to prepare for my interview tomorrow. Thanks!
I keep coming back to this, you need more content like this.
Nice video, just one complaint. Buying domain is from a Domain Registrar, and while they can host your DNS for your domain, that isn't a requirement. For example, our customers have different registrars, but the DNS servers are with the hosting provider that we use, since they have a nice integration for adding their servers to their DNS records, without the chance of mistyping the IP address. And some of the hosting providers give you a much easier to use interface, than some of the registrars. I have over 25 years of experience with DNS servers, and initially, I had to hand edit the records in text files, so I really enjoy the interface provided by some of the hosting providers.
3:45 It's called segmant because we are on transport layer. You use tcp/ip model so I think both packet or segment are the same
5:09 to be more precise, the request includes 3 parts: request line, request header and request body. Same for response, it includes 3 parts: status line, response header and response body
Good catch
@@NeetCode thanks 😊
Wow! This video is impressively well-crafted, managing to be both concise and thorough simultaneously.
This video is the best to just brush up the topics . Thankyou for making this very easy to understand!!!
This was like a flashback of software developers journey ❤
Wow! That took so much knowledge to create such simplicity. Thank you.
The last part summed it up perfectly!
Very good summary of different but related concepts. I wish there were videos like this when I was starting as a Junior Dev 😯
Bro this video must be on Netflix ! what a informative and interesting video ! damn
CDN'S are so polite, would highly recommend one.
I work as a java tech lead in a startup . This will help for next interview
Solid gold. I laughed out loud at the Russell Westbrook inclusion. Love it.
Good review to make sure I still know my basics
Good thing I know almost all concepts and implemented few of them as well
I really loved all the concepts. I'm a front-end heavy full stack developer wanting to upskill in the backend department. These pointers are really helpful. Could anyone point me in the right direction to learn more advanced topics on database designs and it's efficiency?
One of the best videos I see for system design
bro no wonder the name of ur channel is neet because the video i've just watched is so neat really. this is the first time visiting ur channel and i hope i find many more amazing video like this one. Thank u
Thanks for summarising in quick time
This is an AMAZING Systems Design video covering all the key components and explaining them very well.
This is the best system design video i have watched!!
hey i love the way topic more understandable for beginner, thanks 💛
one of the finest videos ever watched...
Clear, concise and precise
This is pure gold for beginners! 🙂
The connection is really helpful. thanks!!
I had to unsubscribe neetcode but I was able to see the network request.
so far the only tech youtuber I have followed whom sticks to tech topics rather than to just film “how to crack the leetcode in 3 months” or “what a day looks like as a sde”😂
The most clever way to get someone to subscribe
I was following your example, but I had to unsubscribe to see the request.
Why so serious !?
@@atomicgray he's joker irl and just reenacting that scene from the movie calm down
😀
@@سيفالباشا-ذ8ع why so serious?
Why did you guys unsubscribed
Bro this video is so much priceless ! It is one of the best or The best I have ever watched ! I learned so much on some specific points. This one should be given to any Junior learner or even Experience dev as well. So glad this one came on my feed.
Amazing work Sir !!
Thanks for the video. Crystal clear.
This is just gold! Thank you!
really cool the way he intertwined these concepts. Also this is the first time ive heard database replication referred to as "leader adn follower". Come on now lol its master and slave instances.
Nicely explained...loved each & every bit of it..!
Knowing these doesn't make you a senior developer, but every senior developer should know every one of these...
Thank you so much, very helpful!
I have a system design interview 3pm today and it's 12pm, so I'm looking into this video.
This entire video is worth years of engineering knowledge
Different concepts are well arranged. It makes super easy to understand them. Do you have more deep explainations?
Very quick and linked information.
Wow! One of the best videos on UA-cam
hey could you add videos focusing on securing the system , and handling payments in your system design course on neetcode.. thankssss
this explanation is just perfect 🤝🤝
Nice and simple... Thank you!
Amazing, this is why I follow you!
I loved your video just in the first 48 seconds
Subscribed already!!! Keep it up!!
very well explained and easy to understand . thanks
absolutely amazing video!
well prepared
My experience with AWS interviews was that no matter how much system design you practice, in the end they're gonna want previous experience with cloud and backend, not just theory. Unless you're applying for a junior role.
junior roles are scarce nowadays they want intermediate at least
Don't mean to be rude but, who asked ?
@@gabrielaudette4591 Anyone with code interview experience should feel comfortable sharing their experiences don’t be a dick lol
@@gabrielaudette4591ironically being incredibly rude in the process
@@garrettfiorito4482 how do you get experience to intermediate if you can’t get experience as a junior? Do you just look for unpaid internships? Sounds unproductive, prob need to know someone who already works there for connections.
Very informative! Thanks
thank you NeetCode, enjoy the show
5:27 Smoothest subscribe bait ever!
You're truly awesome bro
Brief, great video. I love this!
Excellent content mate !
Wow man you did a great explanation in very short time.
This is great! Good job!
Simple & Clear👌🏻