@jxv_2raw: #fyp #couples #dance #relationshipgoals #lockedin

JV
JV
Open In TikTok:
Region: US
Tuesday 14 October 2025 02:38:49 GMT
600055
84286
160
7523

Music

Download

Comments

hearteyes_girl0
Mary❤️ :
Aww STOPP yall are so cute🥺🥰
2025-10-14 11:58:23
508
.iethiano_408
.iethiano_408 :
where the pants from??
2025-10-14 20:30:30
169
oliv6794
Oliv67 :
yes
2025-12-13 05:22:13
0
heyitsjaylah
J a y l a h🐆🤍🎱 :
ya’ll are so cute💗
2025-10-18 17:37:03
2
galimoyeda
𝓖🌺 :
Where did you get the pjs?
2025-10-15 15:46:36
19
aryzzlife
Aryyy🤍 :
Manifesting a relationship like this🙏🙏🙏
2025-11-25 04:57:20
1
sunflower56031
Ms. Sunflower 🌻 :
Your so pretty and cute couple where did u get outfit from ?
2025-11-14 02:35:55
1
genesisperalta1223
Genesis :
Quiero pijamas iguales 🥺🥺🥺
2025-10-15 16:43:00
3
chasearaq
￴￴ :
mbn
2025-10-15 09:25:44
0
_emilia_0909
_emilia_0909 :
cutieee
2025-11-23 02:08:49
0
noelani43
Noelani :
Am wearing the same pants
2025-10-15 01:04:47
4
theodor.tracy
Tracy 👉👈😻💗 :
😍cute
2025-11-22 09:07:49
1
perla.rdz464
Perla rdz :
This is so cute 😭
2025-10-16 05:52:08
283
willow_ur_fav7
Willow🎱🪶♠️ :
@W_Sea04 wo gotta make this
2025-12-15 04:00:57
1
zayyyskii_1
252.K5️⃣ :
@tfw_marie
2025-12-13 05:14:21
1
gabi26583
Gabi :
@Aaron51
2025-11-27 19:58:10
0
payton_777
𖣂︎PAYTON𖣂︎ :
@Mo💫⚽️
2025-11-24 23:16:23
1
itz.calcal
itz.callie💗🦄🥹 :
@Loostin the boostin🛴
2025-11-28 01:54:31
1
dixx_vale
𝓥𝓪𝓵𝓮𝓷𝓽𝓲𝓷𝓪👁️⃤ :
@🕷️ 🤧
2025-12-09 03:05:07
1
a.hewitt4
Alexa :
@cam 😎
2025-12-01 01:08:56
1
andrea.bernard122
andrea.bernard122 :
@✝️Liam🏀⚽️
2025-12-04 02:36:28
1
joey.bishopp
joey :
@່
2025-11-28 03:17:05
1
48vzavery
Zravery❤️‍🔥❤️‍🔥 :
@Ummmmidk
2025-10-28 00:21:43
2
gamalieloliveroo
Gama. :
@Haylee🎀 we need theses
2025-10-25 22:12:12
1
To see more videos from user @jxv_2raw, please go to the Tikwm homepage.

Other Videos

Replying to @starklabs1  Part 3 ~ 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
Replying to @starklabs1 Part 3 ~ 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