@norraaah9: 🩵

Noraa
Noraa
Open In TikTok:
Region: KZ
Thursday 30 July 2026 11:07:17 GMT
18048
1603
30
127

Music

Download

Comments

jan777taraz
*Jan*777* :
красавица от Бога ❤️‍🔥❤️‍🔥❤️‍🔥
2026-07-30 15:55:43
1
kz01sher
Шерхан :
Действительно самая
2026-07-30 20:50:01
0
user219310627080
Хамдам Джуманиязов :
klass😍😍😍
2026-07-30 19:28:14
1
zhas_14pvl0
Жас. 14 PVL :
Скоро станешь моей женой! 🥰
2026-07-30 19:06:28
0
nurzhan_tolendiev099
NURZHAN_TOLENDIEV099 :
садак👍
2026-07-30 19:29:00
0
jasik.b1
. :
Красавица 🥰
2026-07-30 17:45:33
1
user9707016881981
мадияр венгр :
Красота
2026-07-30 17:33:57
0
zhas_14pvl0
Жас. 14 PVL :
2026-07-30 19:05:43
0
user273701079751
ислам маматов :
❤️❤️❤️
2026-07-30 16:20:28
2
user37654427251654
Дидар. Омар :
👸🏻
2026-07-30 14:45:28
0
abdu2603
Abdugaffor :
❤️❤️❤️
2026-07-30 12:28:16
0
natilus27
adsiz :
🍀🍀🍀
2026-07-30 20:24:35
1
gafurov426
gafurov :
🥰🥰🥰
2026-07-30 19:31:03
0
user34567785302103
Аскар Бейсекеев :
🥰🥰🥰🥰🥰🥰🥰🥰🥰
2026-07-30 12:26:43
1
dias_0186
Dias_0186🧿 :
👍👍👍
2026-07-30 19:46:41
0
user9356273903577
Динислам :
🥰🥰🥰
2026-07-30 12:26:01
1
To see more videos from user @norraaah9, please go to the Tikwm homepage.

Other Videos

Part 1 ~ Microservices Will Finally Makes Sense After This Video In this video, Cloud X Berry explains microservices in a simple and beginner-friendly way. Amazon, Netflix, Uber and Spotify ship software updates every single day — and millions of people keep using those apps without ever noticing. That is not luck. It comes down to how the backend is put together, and one of the most popular patterns behind it is called microservices. We start where every application starts: one project, one code base, deployed as one thing. That is a monolith, and for a small app it is genuinely the right choice. Then the team grows, the code base grows, and a three-line bug fix in notifications means rebuilding, retesting and redeploying the entire application. That is the problem microservices were designed to solve. From there we build the idea up piece by piece: splitting by business capability rather than at random, why the split lives in the backend and never touches what the user sees, what actually happens between services when you click Place Order, and what an API contract really is. Then the three advantages that matter — independent deploys, independent scaling, isolated failures — followed by the trade-offs most explainers skip. CHAPTERS 0:00​  Why you never notice an update 0:24​  How applications were traditionally built 0:43​  One project, one code base: the monolith 0:59​  Where the monolith starts to hurt 1:43​  What microservices actually are 2:14​  Splitting by business capability 2:45​  The misconception: backend, not the UI 3:09​  One click, several services 3:37​  What an API really is 3:59​  The API contract 4:39​  Advantage 1: deploy independently 4:56​  Advantage 2: scale independently 5:17​  Advantage 3: failures stay isolated 5:54​  The trade-offs nobody mentions 6:27​  Start with a monolith, move when you grow 6:39​  The one thing to remember WHO THIS IS FOR Developers hearing
Part 1 ~ Microservices Will Finally Makes Sense After This Video In this video, Cloud X Berry explains microservices in a simple and beginner-friendly way. Amazon, Netflix, Uber and Spotify ship software updates every single day — and millions of people keep using those apps without ever noticing. That is not luck. It comes down to how the backend is put together, and one of the most popular patterns behind it is called microservices. We start where every application starts: one project, one code base, deployed as one thing. That is a monolith, and for a small app it is genuinely the right choice. Then the team grows, the code base grows, and a three-line bug fix in notifications means rebuilding, retesting and redeploying the entire application. That is the problem microservices were designed to solve. From there we build the idea up piece by piece: splitting by business capability rather than at random, why the split lives in the backend and never touches what the user sees, what actually happens between services when you click Place Order, and what an API contract really is. Then the three advantages that matter — independent deploys, independent scaling, isolated failures — followed by the trade-offs most explainers skip. CHAPTERS 0:00​ Why you never notice an update 0:24​ How applications were traditionally built 0:43​ One project, one code base: the monolith 0:59​ Where the monolith starts to hurt 1:43​ What microservices actually are 2:14​ Splitting by business capability 2:45​ The misconception: backend, not the UI 3:09​ One click, several services 3:37​ What an API really is 3:59​ The API contract 4:39​ Advantage 1: deploy independently 4:56​ Advantage 2: scale independently 5:17​ Advantage 3: failures stay isolated 5:54​ The trade-offs nobody mentions 6:27​ Start with a monolith, move when you grow 6:39​ The one thing to remember WHO THIS IS FOR Developers hearing "microservices" in every architecture conversation and wanting the idea to actually click, backend engineers weighing up a split, and anyone interviewing for a role where system design comes up. #microservices​ #systemdesign​ #softwarearchitecture​ #backend​ #api​ ​ ​

About