@chillmind.podcast: Du kannst eine Waage nicht einschüchtern Das Sternzeichen, das dich mit seiner Ruhe entwaffnet #tiktokgrowthchallenge #waage #skorpion #steinbock #wassermann

Chill Mind Podcast

Open In TikTok:

Region: US

Monday 21 September 2026 15:19:46 GMT

30691

2140

267

370

Music

Download

No Watermark .mp4 (4.55MB) No Watermark(HD) .mp4 (5.81MB) Watermark .mp4 (4.19MB) Music .mp3

Comments

lotharschuffenhau :

Genau so ist es 22.10😘

2026-09-21 15:55:27

16

lairdmike :

Bin Waage, 27.09, und meine Chefs sind bereits an mir verzweifelt. Wollten mich mit einer Abmahnung weichkochen! Mit einer Abmahnung? Hab Sie angeschaut und nur gefragt und dann? 😁

2026-09-22 11:23:48

10

Kati :

17.10🥰

2026-09-21 16:22:00

7

Kikilemon :

Team Wagge 01.10. 🥰

2026-09-21 18:20:53

6

nadalinaswelt :

Waage ich liebe mein Horoskop [Herzerwärmend]

2026-09-22 16:06:15

5

Brigitte Juhnke :

9.10.

2026-09-21 16:37:11

7

Raphaela Schwaiger :

Ich bin Waage

2026-09-21 16:49:12

8

Ecki :

Wahrheit so bin ich 29.09.🥰

2026-09-21 22:40:19

5

Gabi Kowall :

11.10

2026-09-21 16:56:18

5

Zekirja Gojo :

Ich bin auch wage 27 09 1975

2026-09-21 21:19:50

5

frekigeri4 :

So schaut es aus 💯👍✌️

2026-09-21 18:13:57

5

Hans Jürgen Rössner :

Waage und das ist gut so

2026-09-22 04:25:38

6

Sash Kollmann :

20.10.80

2026-09-21 22:24:43

5

Christine Fröhlich :

Genau so ist es

2026-09-21 17:20:10

6

Dieter_Ropers :

👍100%👍

2026-09-22 07:29:19

5

Marcela Abaziova :

9.10

2026-09-21 16:24:46

5

Aghi100 :

04.10

2026-09-21 21:53:39

5

Jonny😎😇 :

jep😏

2026-09-21 16:58:54

6

Dirk Fieck :

17.10 1972

2026-09-21 22:09:39

6

adrian_zu1_official :

Team Waage ⚖️😊

2026-09-21 16:21:14

6

ramilamursalova :

7.10

2026-09-21 15:50:00

5

mcrose090 :

Ich bin Waage 25.09 und genau so ist es 😁

2026-09-21 18:30:56

9

schlupfie :

17.17.10.1975

2026-09-21 16:42:49

5

edeltrud h :

Realität 20.10.

2026-09-21 15:45:46

5

Paraskevas Wakis Mavrogiannako :

1.10 Hast wieder recht💯

2026-09-21 17:57:07

5

To see more videos from user @chillmind.podcast, please go to the Tikwm homepage.

Other Videos

Quality method lagbe? #Quality #kemon? #60fps#compressbasemethod #viral #tiktok #trending #quality #challenge

Quality method lagbe? #Quality #kemon? #60fps#compressbasemethod #viral #tiktok #trending #quality #challenge

#makeup #fyp

Monolith vs microservices, in one sentence: it's the same app either way. Same five things. Users. Products. Orders. Payments. Notifications. The only thing that changes is where you draw the boundary around them. In a monolith they sit inside one box → 1 codebase, 1 deploy, 1 database, 0 network hops. Calling another part of the app is just a function call. 0.2ms. Simple — and that simplicity is a real advantage. Then you grow. 50 engineers in one merge queue. One line changed means redeploying the entire backend. One bug takes down the whole app. One hot feature and you're scaling all five. So you move the line. Five services. Five deploys. Scale checkout without scaling notifications. Payments ships without asking the search team. But that function call is now a network request. And networks fail. Retries. Timeouts. Service discovery. Load balancing. Distributed tracing. Auth between services. Monitoring. Events. Queues. Idempotency. Eventual consistency. Eleven things you now have to run — before you ship a single feature. Then the payment succeeds and the order service crashes before recording it. And now you're debugging a request that travelled through six services instead of reading one log. Microservices don't remove complexity. They move it. You trade codebase complexity for distributed systems complexity — which is why the answer depends on scale. Five engineers splitting into 30 services on day one is a disaster. A well-structured monolith takes you surprisingly far. Then you extract the painful part. Payments first. Then search. Then notifications. The goal was never more services. It's putting complexity where your team can actually handle it. Which side are you on right now? 👇 #systemdesign #microservices #softwareengineering #backenddev #codingreels

Monolith vs microservices, in one sentence: it's the same app either way. Same five things. Users. Products. Orders. Payments. Notifications. The only thing that changes is where you draw the boundary around them. In a monolith they sit inside one box → 1 codebase, 1 deploy, 1 database, 0 network hops. Calling another part of the app is just a function call. 0.2ms. Simple — and that simplicity is a real advantage. Then you grow. 50 engineers in one merge queue. One line changed means redeploying the entire backend. One bug takes down the whole app. One hot feature and you're scaling all five. So you move the line. Five services. Five deploys. Scale checkout without scaling notifications. Payments ships without asking the search team. But that function call is now a network request. And networks fail. Retries. Timeouts. Service discovery. Load balancing. Distributed tracing. Auth between services. Monitoring. Events. Queues. Idempotency. Eventual consistency. Eleven things you now have to run — before you ship a single feature. Then the payment succeeds and the order service crashes before recording it. And now you're debugging a request that travelled through six services instead of reading one log. Microservices don't remove complexity. They move it. You trade codebase complexity for distributed systems complexity — which is why the answer depends on scale. Five engineers splitting into 30 services on day one is a disaster. A well-structured monolith takes you surprisingly far. Then you extract the painful part. Payments first. Then search. Then notifications. The goal was never more services. It's putting complexity where your team can actually handle it. Which side are you on right now? 👇 #systemdesign #microservices #softwareengineering #backenddev #codingreels

POV: intentas que la visita no se dé cuenta 😭 @Las Ocurrencias De Victor

POV: intentas que la visita no se dé cuenta 😭 @Las Ocurrencias De Victor

please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak

please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak please let me have a winstreak

About

Robot
API

Legal

Privacy Policy