1. Home
  2. Detail

@liz_tina6: Summer vibes ☀️🪶❤️ #fyp #fypシ゚viral #fly #birds #sky

Liz_Tina
Liz_Tina
Open In TikTok:
Region: US
Thursday 20 August 2026 02:22:28 GMT
131
8
0
0

Music

Download

No Watermark .mp4 (3.61MB) No Watermark(HD) .mp4 (3.25MB) Watermark .mp4 (3.25MB) Music .mp3

Comments

There are no more comments for this video.
To see more videos from user @liz_tina6, please go to the Tikwm homepage.

Other Videos

- #DEMITRA - :: did this aud before just added sfx - edit : @geraasfx | tags | #audios #audiosforedits #editaudios #slowededitaudios [ heavly love edit audio slowed overlapped ]
- #DEMITRA - :: did this aud before just added sfx - edit : @geraasfx | tags | #audios #audiosforedits #editaudios #slowededitaudios [ heavly love edit audio slowed overlapped ]
जिन्दगानि दर्पण छाया 🙏 #fyp #peaceful #simpleboy #ekdevlimbusong #lahanalejurayoki
जिन्दगानि दर्पण छाया 🙏 #fyp #peaceful #simpleboy #ekdevlimbusong #lahanalejurayoki
Part 1 ~ The 3 Most Confusing System Design Concepts (Finally Explained) In this video, Cloud X Berry explains the difference between a reverse proxy, a load balancer and an API gateway in a simple and beginner-friendly way. At first glance all three look identical. Each one sits between the client and your application, receives requests and forwards them somewhere else. So why does anyone need three? Because the answer isn't in what they do — it's in the problem each one was built to solve, and that only becomes obvious when you watch the same application grow until it needs all three. We use one example the whole way through: an e-commerce app where users browse products, log in and place orders. First it needs its servers hidden behind one public address — that's the reverse proxy, and we look at the real nginx config, the DNS lookup that proves the private hosts resolve to nothing a client can use, and the extra jobs it picks up on the way: terminating HTTPS, caching, compression, routing. Then traffic grows past what one box can carry, four identical servers go up, and nothing decides which one takes the next request — that's the load balancer, including what actually happens to in-flight traffic the moment a server goes down. Then the backend splits into user, product, order and payment services, and clients suddenly have four base URLs and four separate auth flows to remember — that's the API gateway: authentication, validation, rate limiting and routing, all in front of every request. We finish with the part most explanations skip. These three don't replace each other. We follow one real request through all three in sequence, hop by hop, and end on a straight answer for which one to reach for and when. CHAPTERS 0:00​ Three components that look identical 0:17​ Why three, and not one 0:24​ One example: the cloudXberry app 0:39​ Three problems, three different solutions 0:51​ Reverse proxy: one public address 1:07​ The apartment building front desk 1:34​ Nginx in production 1:48​ Terminating HTTPS, caching, routing 1:58​ One server is no longer enough 2:13​ Load balancer: spreading the traffic 2:25​ When a server goes down 2:30​ The supermarket checkout analogy 2:41​ Splitting into microservices 3:02​ API gateway: one guarded door 3:19​ The airport check-in counter 3:51​ Recap: reverse proxy 4:05​ Recap: load balancer 4:19​ Recap: API gateway 4:38​ They don't replace each other 4:42​ One request through all three 4:55​ Knowing when and why WHO THIS IS FOR Developers who keep seeing all three boxes in architecture diagrams and want to know which one they're actually looking at, backend engineers about to put something in front of their servers and unsure which of the three it should be, and anyone interviewing for a role where system design or API architecture comes up. #reverseproxy​ #loadbalancer​ #apigateway​ #systemdesign​ #backend​ ​ ​
Part 1 ~ The 3 Most Confusing System Design Concepts (Finally Explained) In this video, Cloud X Berry explains the difference between a reverse proxy, a load balancer and an API gateway in a simple and beginner-friendly way. At first glance all three look identical. Each one sits between the client and your application, receives requests and forwards them somewhere else. So why does anyone need three? Because the answer isn't in what they do — it's in the problem each one was built to solve, and that only becomes obvious when you watch the same application grow until it needs all three. We use one example the whole way through: an e-commerce app where users browse products, log in and place orders. First it needs its servers hidden behind one public address — that's the reverse proxy, and we look at the real nginx config, the DNS lookup that proves the private hosts resolve to nothing a client can use, and the extra jobs it picks up on the way: terminating HTTPS, caching, compression, routing. Then traffic grows past what one box can carry, four identical servers go up, and nothing decides which one takes the next request — that's the load balancer, including what actually happens to in-flight traffic the moment a server goes down. Then the backend splits into user, product, order and payment services, and clients suddenly have four base URLs and four separate auth flows to remember — that's the API gateway: authentication, validation, rate limiting and routing, all in front of every request. We finish with the part most explanations skip. These three don't replace each other. We follow one real request through all three in sequence, hop by hop, and end on a straight answer for which one to reach for and when. CHAPTERS 0:00​ Three components that look identical 0:17​ Why three, and not one 0:24​ One example: the cloudXberry app 0:39​ Three problems, three different solutions 0:51​ Reverse proxy: one public address 1:07​ The apartment building front desk 1:34​ Nginx in production 1:48​ Terminating HTTPS, caching, routing 1:58​ One server is no longer enough 2:13​ Load balancer: spreading the traffic 2:25​ When a server goes down 2:30​ The supermarket checkout analogy 2:41​ Splitting into microservices 3:02​ API gateway: one guarded door 3:19​ The airport check-in counter 3:51​ Recap: reverse proxy 4:05​ Recap: load balancer 4:19​ Recap: API gateway 4:38​ They don't replace each other 4:42​ One request through all three 4:55​ Knowing when and why WHO THIS IS FOR Developers who keep seeing all three boxes in architecture diagrams and want to know which one they're actually looking at, backend engineers about to put something in front of their servers and unsure which of the three it should be, and anyone interviewing for a role where system design or API architecture comes up. #reverseproxy​ #loadbalancer​ #apigateway​ #systemdesign​ #backend​ ​ ​
#سجه_مع_الهاجوس# #روعه____جميل🌹_ذوق_🌹تصميمي🎼 سعد_الشراري_إكسبلوررر
#سجه_مع_الهاجوس# #روعه____جميل🌹_ذوق_🌹تصميمي🎼 سعد_الشراري_إكسبلوررر


#صباح_الخير #fypシ゚viral #اكسبلورر #تصاميم_فيديوهات #capcut
#صباح_الخير #fypシ゚viral #اكسبلورر #تصاميم_فيديوهات #capcut

About

Legal