@romariz.021:

Romariz RJ
Romariz RJ
Open In TikTok:
Region: BR
Thursday 24 September 2026 03:32:45 GMT
249475
28616
231
471

Music

Download

Comments

qu3iroz02
QueiroZ :
Acho que é normal mn, meu iPhone 3 tbm tá assim
2026-09-24 15:03:29
1104
eufelpsoliver
eufelpsoliver17 :
O celular também com 200 graus depois dele gravar 100 vídeos seguidos
2026-09-24 07:42:57
3525
davi.thoms.figuei
Davi :
quer postar 30 videos ao mesmo tempo
2026-09-24 10:23:47
425
mumuxisl
rato :
Romariz compra o celular redmagic 11 pro 16gb 512gb 5g nightfreeze ele se auto resfria e não tem travamentos
2026-09-24 05:03:16
36
tonton___0
branks1️⃣4️⃣ :
1 vídeo da madruga
2026-09-24 05:07:16
340
brnwo_
breno :
e há quem diga que é superior a samsung KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
2026-09-24 12:45:23
156
fredsonrlq
du7🏌🏾 :
Celular novo é assim msm loko, o meu travava pra crlh tbm logo quando comprei
2026-09-24 20:54:57
24
alan53637jdn.ys
@stxrly :
eu ainda tô com o meu 17 e vou continuar com ele
2026-09-24 15:38:42
23
francosx__
 :
Normal chefe meu iPhone 2 tá assim tb
2026-09-24 22:48:35
24
marcosbielxt
Marcos. :
ele caindo no ragebait kkkkkk
2026-09-24 04:13:37
36
queixinho__
🥸 :
Acho q todo iPhone tá assim,meu tbm tá assim
2026-09-24 05:59:19
16
k3vin1235
K :
obs:e um Samsung com carcaça de iPhone 18
2026-09-24 22:54:26
4
sleyx_xxx
x.SLEY.x :
o meu moto g05 é melhor
2026-09-24 11:09:40
19
ana.estela394
Amanda✨ :
Na sua casa durmo aonde???😳😅🥰
2026-09-24 03:42:49
9
adelino_jr4
@Adeli.G :
o meu tá o mesmo mais n iphone 18 é 14 tá travando
2026-09-24 06:05:48
6
nk.gomesz
eugomesz :
2026-09-24 22:57:07
1
vzzsbritto
vzzbritto :
me doa ele então mno
2026-09-24 22:11:55
0
melancholy_012
kaelzsx. :
isso é a net
2026-09-24 17:07:37
0
peterson1257
あかはま :
nem meu poço c85 trava
2026-09-24 23:53:44
0
lilmillys7
🥷 :
pior que iPhone realmente trava, por mais otimizado que seja, não tenho um, mas já usei o dos outros e o meu poco e bem mais tranquilo
2026-09-25 01:27:40
0
rlk_souzax3
￴￴ ￴ ￴ ￴￴ ￴ ￴ ￴ ￴￴ ￴ ￴ ￴ :
por isso q eu n compro
2026-09-24 21:50:16
3
danielzzk_bs
danielzzk :
por isso prefiro meu @galaxy a54 11 hora de duração eu jogo jogos pesados e nem trava
2026-09-24 15:37:29
2
marquezx__00
marquezx__00 :
PRIMEIRO
2026-09-24 03:35:10
0
eur1ck
Rick e 🔝 :
Man geral sabe que é assim, comprar na pré venda é sempre ter dor de cabeça. Foi igual com o 17 pro max
2026-09-24 15:58:14
2
davizinhu_777
@danzyndits :
Cara reclamando e eu aq com meu Redmi 5 plus kkkk
2026-09-24 07:45:21
2
To see more videos from user @romariz.021, please go to the Tikwm homepage.

Other Videos

Load balancer. Cache. Queue. CDN. Replica. Shard. 🧠 If those sound like a pile of random buzzwords, this one's for you. Here's the secret: nobody sits down and designs a system with 9 components. You start with ONE server, and every new piece gets added because something broke. Here's the whole thing in order 👇 1️⃣ One server can't keep up → add more servers + a load balancer 2️⃣ Every server hammers the same database → add a cache (Redis) 3️⃣ Reads keep growing → add read replicas 4️⃣ One database can't hold it all → shard the data 5️⃣ Photos and videos bloat the database → move them to object storage (S3 / R2) 6️⃣ Users far away wait forever → put a CDN in front 7️⃣ Uploads make users wait on slow jobs → add a queue + background workers 8️⃣ Servers crash, regions disappear → build in redundancy 9️⃣ You can't see what's breaking → add observability (logs, metrics, traces) And the biggest beginner mistake? Adding Kafka, Kubernetes, microservices and 10 databases before you have a real problem. Every component has a cost: • caches go stale • queues deliver twice • replicas lag • shards make queries harder • microservices fail over the network So the real skill isn't memorizing tools. It's asking one question: 👉
Load balancer. Cache. Queue. CDN. Replica. Shard. 🧠 If those sound like a pile of random buzzwords, this one's for you. Here's the secret: nobody sits down and designs a system with 9 components. You start with ONE server, and every new piece gets added because something broke. Here's the whole thing in order 👇 1️⃣ One server can't keep up → add more servers + a load balancer 2️⃣ Every server hammers the same database → add a cache (Redis) 3️⃣ Reads keep growing → add read replicas 4️⃣ One database can't hold it all → shard the data 5️⃣ Photos and videos bloat the database → move them to object storage (S3 / R2) 6️⃣ Users far away wait forever → put a CDN in front 7️⃣ Uploads make users wait on slow jobs → add a queue + background workers 8️⃣ Servers crash, regions disappear → build in redundancy 9️⃣ You can't see what's breaking → add observability (logs, metrics, traces) And the biggest beginner mistake? Adding Kafka, Kubernetes, microservices and 10 databases before you have a real problem. Every component has a cost: • caches go stale • queues deliver twice • replicas lag • shards make queries harder • microservices fail over the network So the real skill isn't memorizing tools. It's asking one question: 👉 "What problem forced us to add this?" Start simple. Find the bottleneck. Add the smallest fix. Repeat. 💾 Save this for your next system design interview 💬 Which of the 9 steps did you learn the hard way? Tell me in the comments 👇 #systemdesign #softwareengineering #backenddevelopment #codinginterview #learntocode

About