@nannybb_9597: มาถามอะไรแบบนี้ในที่สาธารณะ🤭 กอล์ฟถามพายแบบนี้แม่ก็เขินแย่เลย @pie_saran @golfpasatorn #พายกอล์ฟ #pie_saran 🐯 | #เตาอบตัวพี 🥧 #golfpasatorn ⛳️ | #แคดดี้ของแป๊ะยิ้ม 🍭

NannyBB9597
NannyBB9597
Open In TikTok:
Region: TH
Wednesday 23 September 2026 12:57:22 GMT
1975
254
3
6

Music

Download

Comments

dyypod2h3353
ออมสินสมประสงค์ :
ระวังเสือขะย้ำนะยายหนาวอย่าล้อเล่นกับบกมาเฟืย
2026-09-24 02:59:56
2
kanjananulin
Nu..lin.. :
น่ารัก
2026-09-24 00:33:58
1
nongdow29
Nong Dowสาวไต🐷 :
2026-09-24 05:14:21
1
To see more videos from user @nannybb_9597, please go to the Tikwm homepage.

Other Videos

Load balancer. Cache. Queue. CDN. Replica. Shard. 🧠 If those sound like a pile of random buzzwords, this one's for you. Here's the secret: nobody sits down and designs a system with 9 components. You start with ONE server, and every new piece gets added because something broke. Here's the whole thing in order 👇 1️⃣ One server can't keep up → add more servers + a load balancer 2️⃣ Every server hammers the same database → add a cache (Redis) 3️⃣ Reads keep growing → add read replicas 4️⃣ One database can't hold it all → shard the data 5️⃣ Photos and videos bloat the database → move them to object storage (S3 / R2) 6️⃣ Users far away wait forever → put a CDN in front 7️⃣ Uploads make users wait on slow jobs → add a queue + background workers 8️⃣ Servers crash, regions disappear → build in redundancy 9️⃣ You can't see what's breaking → add observability (logs, metrics, traces) And the biggest beginner mistake? Adding Kafka, Kubernetes, microservices and 10 databases before you have a real problem. Every component has a cost: • caches go stale • queues deliver twice • replicas lag • shards make queries harder • microservices fail over the network So the real skill isn't memorizing tools. It's asking one question: 👉
Load balancer. Cache. Queue. CDN. Replica. Shard. 🧠 If those sound like a pile of random buzzwords, this one's for you. Here's the secret: nobody sits down and designs a system with 9 components. You start with ONE server, and every new piece gets added because something broke. Here's the whole thing in order 👇 1️⃣ One server can't keep up → add more servers + a load balancer 2️⃣ Every server hammers the same database → add a cache (Redis) 3️⃣ Reads keep growing → add read replicas 4️⃣ One database can't hold it all → shard the data 5️⃣ Photos and videos bloat the database → move them to object storage (S3 / R2) 6️⃣ Users far away wait forever → put a CDN in front 7️⃣ Uploads make users wait on slow jobs → add a queue + background workers 8️⃣ Servers crash, regions disappear → build in redundancy 9️⃣ You can't see what's breaking → add observability (logs, metrics, traces) And the biggest beginner mistake? Adding Kafka, Kubernetes, microservices and 10 databases before you have a real problem. Every component has a cost: • caches go stale • queues deliver twice • replicas lag • shards make queries harder • microservices fail over the network So the real skill isn't memorizing tools. It's asking one question: 👉 "What problem forced us to add this?" Start simple. Find the bottleneck. Add the smallest fix. Repeat. 💾 Save this for your next system design interview 💬 Which of the 9 steps did you learn the hard way? Tell me in the comments 👇 #systemdesign #softwareengineering #backenddevelopment #codinginterview #learntocode

About