@thom.code: 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​ ​ ​

Thom Code
Thom Code
Open In TikTok:
Region: NG
Thursday 30 July 2026 06:33:10 GMT
22229
1372
16
104

Music

Download

Comments

sarmizofficiall
Sarmiz :
Modular Monolith is better for a startup, but must be built in a way to be able to be extracted into it own micro service
2026-07-30 12:21:35
14
bobod24.4
Bobo D :
how can i apply this to a desktop application cath runs mostly offline electron js
2026-07-30 19:43:40
0
zay500000
Zay :
Thank you
2026-07-30 20:24:08
0
bruno.miguel.esteves
Bruno Miguel :
I do believe that the name “micro-services” is wrongly used! What it really means is “domain services”
2026-07-30 09:42:50
6
bozon_jnr
@BOZON 👷 :
this video talk to me 😁 thanks
2026-07-30 08:23:30
4
chukwuebukagwam
Ultragem | Web Developer :
part 2!!!!!
2026-07-30 17:38:18
1
molebogeng_selahle
Molebogeng :
full video?
2026-07-30 16:05:16
1
benjaminsdevs
:
we do know when it happens
2026-07-30 16:46:21
0
codecareertips
codecareertips :
This was really helpful
2026-07-30 17:09:12
0
jrbrann
jrbrann :
Wow
2026-07-30 11:01:08
0
fopa_baurel
… :
Part 2??
2026-07-30 13:47:50
0
To see more videos from user @thom.code, please go to the Tikwm homepage.

Other Videos


About