@amin.m101: هدفين ميسي اليوم😍🔥 #everyone #ميسي🇦🇷 #تصميم_فيديوهات🎶🎤🎬 #team_fav🏹🦅 #foryou

𝐅𝐀𝐕 𝐀𝐌𝐈𝐍🏅

Open In TikTok:

Region: EG

Sunday 11 October 2026 01:16:40 GMT

9574

1077

6

124

Music

Download

No Watermark .mp4 (2MB) No Watermark(HD) .mp4 (1.72MB) Watermark .mp4 (3.58MB) Music .mp3

Comments

Zezo :

التاريخ

2026-10-11 11:10:44

1

mohamed :

4-0 بعد اعتزاله دوليآ ياجماعه ده ازاااي يعتزل

2026-10-11 08:19:54

4

🇦🇷꧁༺Atiya༻꧂❤ :

2026-10-11 05:31:32

2

Barca 🇪🇦💙♥️ :

ماشي ماتسيبناش 🥰

2026-10-11 03:03:26

0

yaseen gehad :

❤️❤️❤️

2026-10-11 10:22:58

0

احمد جابر :

🥰🥰🥰

2026-10-11 08:26:53

0

𝑭𝑨𝑽/𝑻𝒂𝒉𝒂 :

😍😍😍

2026-10-11 01:21:15

0

Malek 🥷🏻☝🏻 :

♥️♥️♥️

2026-10-11 11:06:35

0

To see more videos from user @amin.m101, please go to the Tikwm homepage.

Other Videos

Most people learn these in the wrong order. ⚡ They start with Circuit Breaker because it sounds impressive. But the breaker only exists because retries made things worse — and retries only exist because of timeouts. 12 patterns, in the order they actually build on each other 👇 🟢 FAIL FAST 1. Timeout — cut it at 200ms, not 30s. A hung call still holds a thread. 2. Retry — backoff doubles: 1s, 2s, 4s. Jitter stops the thundering herd. 3. Circuit breaker — closed, open, half-open. One probe decides, not a timer. 🔵 PROTECT CAPACITY 4. Rate limiter — the 11th request gets a 429. Shed early, or shed everything. 5. Bulkhead — cart drowns, auth still serves. One pool per dependency. 6. Pub/Sub — one publish, three consumers. The publisher never waits. 🟡 CACHING & STATE 7. Cache aside — miss, fetch, then set. The app owns the cache, not the DB. 8. Write-through — no ack until the DB has it. Slower writes, never a stale read. 9. Event sourcing — replay the log, rebuild the state. Never overwrite, only append. 🟣 DISTRIBUTED, THE HARD PART 10. CQRS — the read side lags, on purpose. Scale reads without slowing writes. 11. Saga — step 3 fails, so undo 2 then 1. There is no distributed rollback. 12. Strangler fig — route by route, never a big bang. The old system dies last. 👀 The one nobody says: a retry without a breaker is an outage generator. Your dependency degrades, every caller retries, and the retries become the traffic that kills it. The rule: never add a retry without deciding when to stop retrying. Most engineers can name all 12 and can't say which two fight each other. That's the real interview question. 📸 Screenshot the grid. Save it before your next design round. Follow @hackproduct — we turn scary engineering concepts into things you can ship. ⚡ . . #systemdesign #softwareengineering #systemdesigninterview #backend #distributedsystems

Most people learn these in the wrong order. ⚡ They start with Circuit Breaker because it sounds impressive. But the breaker only exists because retries made things worse — and retries only exist because of timeouts. 12 patterns, in the order they actually build on each other 👇 🟢 FAIL FAST 1. Timeout — cut it at 200ms, not 30s. A hung call still holds a thread. 2. Retry — backoff doubles: 1s, 2s, 4s. Jitter stops the thundering herd. 3. Circuit breaker — closed, open, half-open. One probe decides, not a timer. 🔵 PROTECT CAPACITY 4. Rate limiter — the 11th request gets a 429. Shed early, or shed everything. 5. Bulkhead — cart drowns, auth still serves. One pool per dependency. 6. Pub/Sub — one publish, three consumers. The publisher never waits. 🟡 CACHING & STATE 7. Cache aside — miss, fetch, then set. The app owns the cache, not the DB. 8. Write-through — no ack until the DB has it. Slower writes, never a stale read. 9. Event sourcing — replay the log, rebuild the state. Never overwrite, only append. 🟣 DISTRIBUTED, THE HARD PART 10. CQRS — the read side lags, on purpose. Scale reads without slowing writes. 11. Saga — step 3 fails, so undo 2 then 1. There is no distributed rollback. 12. Strangler fig — route by route, never a big bang. The old system dies last. 👀 The one nobody says: a retry without a breaker is an outage generator. Your dependency degrades, every caller retries, and the retries become the traffic that kills it. The rule: never add a retry without deciding when to stop retrying. Most engineers can name all 12 and can't say which two fight each other. That's the real interview question. 📸 Screenshot the grid. Save it before your next design round. Follow @hackproduct — we turn scary engineering concepts into things you can ship. ⚡ . . #systemdesign #softwareengineering #systemdesigninterview #backend #distributedsystems

Lupa Zalupa Coca-Cola Explosion 😂🥤💥 #LupaZalupa #Brainrot #FunnyAnimation #CocaCola #FoamExplosion

Lupa Zalupa Coca-Cola Explosion 😂🥤💥 #LupaZalupa #Brainrot #FunnyAnimation #CocaCola #FoamExplosion

#рек#реки#рекомендации #лубовь #боль

#рек#реки#рекомендации #лубовь #боль

Passenger Rail Network in The United States vs Europe.

Passenger Rail Network in The United States vs Europe.

مـ ريتــه يحــط فـي الســـاق خلخــالي❣️#اكسبلور #until #هشتاقاتي_الترند_المشهور #foryoupage #ynghiacuocsong @الفنانة راكس 🎙

مـ ريتــه يحــط فـي الســـاق خلخــالي❣️#اكسبلور #until #هشتاقاتي_الترند_المشهور #foryoupage #ynghiacuocsong @الفنانة راكس 🎙

Mờ ê meeeee 🎬 Á:N M:ẠNG XÉM HOÀN HẢO | ĐANG CHIẾU TẠI RẠP #DJMie #AnMangXemHoanHao #AnMangXemHoanHaobySBNB #ShowbizNhatBao #TiktokGiaiTri

Mờ ê meeeee 🎬 Á:N M:ẠNG XÉM HOÀN HẢO | ĐANG CHIẾU TẠI RẠP #DJMie #AnMangXemHoanHao #AnMangXemHoanHaobySBNB #ShowbizNhatBao #TiktokGiaiTri

About

Robot
API

Legal

Privacy Policy