1. Home
  2. Detail

@davidviorelionut:

David Viorel Ionuț
David Viorel Ionuț
Open In TikTok:
Region: RO
Tuesday 22 September 2026 12:14:25 GMT
261
21
2
2

Music

Download

No Watermark .mp4 (2.56MB) No Watermark(HD) .mp4 (2.56MB) Watermark .mp4 (2.56MB) Music .mp3

Comments

nicuion87
Nicu Ion :
😂😂😂
2026-09-22 17:47:42
1
To see more videos from user @davidviorelionut, please go to the Tikwm homepage.

Other Videos

Wait until the end…😳
Wait until the end…😳
#CapCut #বড় একা একা লাগে আমার....... লাগেনা ভালো আর... .. 😔🥀🖤.......!fyp foryoupage.....😔🥀
#CapCut #বড় একা একা লাগে আমার....... লাগেনা ভালো আর... .. 😔🥀🖤.......!fyp foryoupage.....😔🥀
MONO xuất hiện với visual miễn chê ngay tại sự kiện Cư Xá adidas #adidasVietnam #WorldCup #CuXaadidas #mono
MONO xuất hiện với visual miễn chê ngay tại sự kiện Cư Xá adidas #adidasVietnam #WorldCup #CuXaadidas #mono
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
gua dan bro ini mah #newchapter #killerpeter #manhwareccomendation #masukberandafyp #fakesituation @Rvenn – am prem dibio
gua dan bro ini mah #newchapter #killerpeter #manhwareccomendation #masukberandafyp #fakesituation @Rvenn – am prem dibio
#أحمد_البرقاوي #محمد_المقحم #خواطر #اكسبلور #تصويري
#أحمد_البرقاوي #محمد_المقحم #خواطر #اكسبلور #تصويري

About

Legal