System Design Kya Hai? Zero Se Samjho (Hinglish) | Day 1 | The Junior Dev
The Junior Dev
0:00 / 0:00
System Design Kya Hai? Zero Se Samjho (Hinglish) | Day 1 | The Junior Dev
68 просмотров · 14 ч назад
The Junior Dev
9 подписчиков
68 просмотров · 14 ч назад
System Design zero se, simple Hinglish mein. Day 1 mein samjho system design kya hai, kyun zaroori hai, kyun seekhna chahiye, aur 15 basic shabd, phir saath mein ek real app (college canteen) ka pehla design.
Koi heavy jargon nahi, koi ratta nahi. Tatkal booking, chai tapri, UPI payment jaise roz ke examples aur animated diagrams.
⏱ CHAPTERS
0:00 Hook: Tatkal 10 baje kyun atakta hai
1:25 Main kaun hoon + is series mein kya milega
2:34 App ke peeche kya hai (client, server, database)
5:40 Ek din, 5 apps
8:27 System design kya hai? Raju ki chai tapri
11:39 Zaroorat kyun? 4 problems
14:34 Kyun seekhein + 4 myths
17:44 Dictionary 1: scale, latency, throughput, availability
20:49 Dictionary 2: bottleneck, peak, redundancy, requirements, trade-off
24:04 HLD vs LLD
28:42 System designer ke 4 steps
30:33 Saath mein design: college canteen app
35:43 Kaise seekhein + series roadmap
37:49 Recap + homework
📝 NOTES (Day 1)
Notes : https://claude.ai/artifact/2UynCcTf4p...
1. Har app = Client (jo maangta hai) + Server (jo kaam karta hai) + Database (jo yaad rakhta hai). Client request bhejta hai, server response deta hai.
2. Har app 2 kaam karti hai: padhna (read) aur likhna (write).
3. System design = software ko aise plan karna ki woh sahi kaam kare, bheed sambhale, aur kuch kharab ho toh poora na toote.
4. Bina design ke 4 problems: slow, band (downtime), data loss/galat data, bekaar kharcha. Lekin pehle din se over-engineering bhi galti.
5. Dictionary:
• Scale: badhna aur badhne par sambhalna
• Latency: ek kaam ka intezaar (ms mein). Throughput: ek tay time mein kitna kaam
• Availability: system kitne time chalu raha
• Bottleneck: sabse patla raasta jo poore system ko dheema kare
• Peak: sabse zyada bheed ka time; design peak ke liye karo
• Redundancy: zaroori cheez ka extra copy
• Functional requirements = kya karega; Non-functional = kitna achha (speed, uptime, sahi data)
• Trade-off: kuch paane ke liye kuch chhodna
6. HLD = poore system ka naksha (boxes + arrows). LLD = ek hisse ke andar ka code design (classes, unke rishte).
7. Designer ke 4 steps: Samjho (requirements) → Andaza (users, peak) → Simple naksha → Kamzori dhoondho, phir sudhaaro.
8. Canteen app: 600 orders / 15 min ≈ 40/min, 1 request/sec se kam. Kamzoriyan: ek server, data backup nahi, aur asli bottleneck kitchen.
🏠 HOMEWORK
Apni roz ki ek app chuno aur likho: client kaun, server se kya maangte hain, database mein kya data, peak kab, aur bottleneck kahan hoga. Jawab comments mein!
➡️ Next: Day 2 · Ek request ka safar (client se server tak, step by step)
📲 Short reels: / the.junior.dev
👍 Video kaam ka laga toh like karo, share karo, aur subscribe karo taaki Day 2 miss na ho.
#systemdesign #systemdesigninhindi #backend #hld #lld #thejuniordev