Skip to content
Hallway
0:00 / 0:00

#systemdesign#loadbalancers#caching

20 System Design Concepts Explained in 10 Minutes

NeetCode

1.1M subscribers • 1 video on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Navdeep Singh, creator of NeetCode

Beginner. No background in the topic needed.

1.7M views3 years ago1 recommendation

Software designDistributed systemsSystem design interviewsSoftware architectureScaling and large-scale architecture

Navdeep Singh provides a rapid overview of twenty key system design concepts, from scaling and load balancers to databases and message queues.

🚀 neetcode.io/ - A better way to prepare for coding interviews! A brief overview of 20 system design concepts for system design interviews. Checkout my second Channel: @NeetCodeIO 🧑‍💼 LinkedIn: linkedin.com/in/navdeep-singh-3aaa14161/ 🥷 Discord: discord.gg/ddjKRXPqtk 🐦 Twitter: twitter.com/neetcode1 📷 Instagram: instagram.com/neetcodeio/ 🎵 TikTok: tiktok.com/@neetcode.io - Intro - Vertical Scaling - Horizontal Scaling - Load Balancers - Content Delivery Networks - Caching - IP Address - TCP / IP - IP Address - Domain Name System - HTTP - REST - GraphQL - gRPC - WebSockets - SQL - ACID - NoSQL - Sharding - Replication - CAP Theorem - Message Queues For sponsorship inquiries please reach out to mail@neetcode.io #system #design #interview

Why it's here

1 person recommends this

What people say. Recommended as a quick and clear overview of fundamental system design concepts for interviews and general knowledge.

Moments people linked to

u/Ok_Remove3123in r/node • Recommends

On “What exactly is REST API? And what is the difference between REST and GraphQL?”

watch this youtube video, it has a couple of minutes on it and it is very good
31View on Reddit

u/greenplant2222in r/SystemDesign • Mentions

Webhooks for Chat Apps? This system design video cites Websockets as an alternative to HTTP polling for chat applications. I get websocket's advantages over polling and, for many applications, I get webhooks advantages over polling, however, I don't know if I'm understanding the benefits of a websocket over webhooks for chat apps or any apps. Could someone help me understand? My guesses: - "..." preview function for chat apps might result in many web requests, potentially making it hard to distinguish from a DDOS attack? - Group chats - maybe you only need 1 webocket connection versus having to maintain a many-to-1 webhook relationship?
1View on Reddit