@khunphachan_ptt: ซีนนี้เลย ชอบวะ #twnpich #porsuppakarn #teeteepor

คุณพระจันทร์ ☾
คุณพระจันทร์ ☾
Open In TikTok:
Region: TH
Wednesday 01 April 2026 14:07:10 GMT
316651
73554
157
3388

Music

Download

Comments

txeyxiw
มูมุ :
ละคือตามนิยายเป๊ะ นึกว่าจะไม่ได้ดูฉากนี้สะแล้ว
2026-04-01 14:43:44
1641
_sushi321
ซูชิแมวดำ :
คือร้องตามด้วงอ่ะคือแบบคิดไม่ออกจริงๆว่าถ้าฉินทิ้งจริงๆมันจะออกมาเป็นรูปแบบไหน😭
2026-04-01 14:32:54
710
nmilase
nmilase :
Can they really put this scene in series 🤭😂 It's so adorable 😂🤭
2026-04-01 19:25:53
122
__woonsen_
__woonsen_ :
ออกมาจากในนิยายเป๊ะๆเลยเทอออ เอ็นดูร้องไห้อ่าาา🥺
2026-04-01 21:06:55
277
karmaz69_555
เมดิสัน แซ่ตึ๋ง :
รุ่นนี้ขนตาไม่เคยแห้ง
2026-04-01 22:23:35
232
121400q
เบ๊บ🐰 :
เป็นคำว่า เฮงซวย ที่น่ารักมากกก
2026-04-01 14:45:33
558
ololaroax
ololaroax :
น่ารักชิบหายเลย555555🥺😭😭
2026-04-01 18:32:09
128
tangmay687
Ja Ae :
ปิ๊บก็ตัวแค่นี้🥰🥰
2026-04-01 14:43:31
47
poy_20096
ᴘᴏʏ☾ :
เศร้าเลยมั้ยทีนี้555448373
2026-04-01 14:11:20
238
whitelovely23
White :
awhh baju nya duang dipakai qin 🥰🥰
2026-04-02 00:23:35
81
yaipewww
Chocolate inq :
ละชันเอ็นดูจนขำอ่ะแกร่55555555😂😂
2026-04-01 14:58:49
74
su09_vava
SU09_VAVA🌟 :
เติมปิ๊ปๆๆๆ
2026-04-01 14:41:53
41
user7370865409787
ฮ่ะ :
ด้วงมันน่ารักง่ะ
2026-04-01 14:44:06
52
boomchol
bocho.teepensawY :
เทอออออ ตอนอ่านอ่ะ ร้องไห้ตามเลยอ่ะ คืออินตามด้วงงงอ่ะ ไม่คิดว่าจะได้ดูซีนนี้
2026-04-01 14:51:42
122
23marvscxae
Samoyd :
ยิ่งกว่าเด็กโกล์ดเด้นจริงๆ
2026-04-01 22:54:59
24
palaop
โกโก้ไม่หวาน :
อยากรู้ว่าฉินเคยรู้สึกว่ามีลูกมากกว่ามีแฟนมั้ย5555554
2026-04-01 18:07:32
71
nutc.p
Nuch shop. 🛒 :
เป็นการด่าว่าเฮงซวยที่โกรธไม่ลงเลยจริงๆ
2026-04-01 23:35:08
25
babikongjro
Malee_มาลี🌺 :
Qin really left Duang, it's so sad that I cried all night, lost my house 555😆😆
2026-04-02 12:40:40
9
aiyhcdgj1
🦋 :
พูดออกมาได้เฮงซวย😂😂
2026-04-02 00:13:59
10
momharitt
อยากเป็นแม่เจ่งเจ่ง :
ขี้อ้อนจังวะะ
2026-04-02 05:01:16
9
p.tume0104
She Oabb :
เป็นการด่าที่กุขำมาก55555555666776555
2026-04-02 12:21:26
7
pimnoupinoum
Only_A_Moment😎😎 :
น่ารักกกก😆
2026-04-01 14:50:37
23
palaop
โกโก้ไม่หวาน :
ทำไมน่ารักขนาดนนี้ว้ะเนี้ย555555
2026-04-01 18:04:40
16
To see more videos from user @khunphachan_ptt, please go to the Tikwm homepage.

Other Videos

Part 1 ~ RabbitMQ Will Finally Makes Sense After This Video in this video, Cloud X Berry explains RabbitMQ in a simple and beginner-friendly way. You tap Transfer on your banking app and the confirmation appears instantly. Behind that screen, fraud detection is still running, the balance still needs updating, a notification still has to go out and the transaction still has to reach the ledger. None of it has finished. That is not a shortcut — it is a message broker doing its job, and RabbitMQ is the one most teams reach for. We start with the version that has no broker: the banking service calls fraud detection and waits, calls the balance service and waits, calls notifications and waits. Every transfer feels slow. Worse, if the notification service happens to be down, a perfectly good payment fails. Neither of those is acceptable, and both come from the same cause — services calling each other directly. From there we build the idea up piece by piece: what a broker actually sits between, what a producer and a consumer really are, why you publish to an exchange instead of straight to a queue, and how bindings and routing keys decide where a message ends up. We go through all four exchange types, then queues as a buffer during a traffic spike, scaling out with multiple consumers, and the ordering guarantee you give up when you do. Then the part most tutorials rush — what happens when a consumer crashes mid-transaction: acknowledgements, redelivery, why your consumers have to be idempotent, retries, dead letter queues, durable queues, publisher confirms and quorum queues. We finish with an honest comparison against Apache Kafka and a straight answer on which one to reach for. CHAPTERS 0:00​  The transfer that feels instant 0:13​  What still has to happen after you tap Transfer 0:34​  The problem RabbitMQ was built to solve 0:54​  One transfer, step by step 1:11​  Producers, consumers and the broker 1:21​  Exchanges, bindings and routing keys 1:43​  Direct, fanout, topic and headers exchanges 2:15​  Queues, buffering and traffic spikes 2:34​  Scaling out with multiple consumers 2:52​  A consumer crashes: acks, redelivery, idempotency 3:23​  Retries and dead letter queues 3:41​  Durability, publisher confirms and quorum queues 4:07​  RabbitMQ vs Apache Kafka 4:40​  When to use which 4:58​  Recap WHO THIS IS FOR Developers who keep seeing RabbitMQ in architecture diagrams and want the idea to actually click, backend engineers about to put a queue in front of work that currently makes every request wait, and anyone interviewing for a role where asynchronous messaging or system design comes up. #rabbitmq​ #messagequeue​ #systemdesign​ #backend​ #microservices​ ​
Part 1 ~ RabbitMQ Will Finally Makes Sense After This Video in this video, Cloud X Berry explains RabbitMQ in a simple and beginner-friendly way. You tap Transfer on your banking app and the confirmation appears instantly. Behind that screen, fraud detection is still running, the balance still needs updating, a notification still has to go out and the transaction still has to reach the ledger. None of it has finished. That is not a shortcut — it is a message broker doing its job, and RabbitMQ is the one most teams reach for. We start with the version that has no broker: the banking service calls fraud detection and waits, calls the balance service and waits, calls notifications and waits. Every transfer feels slow. Worse, if the notification service happens to be down, a perfectly good payment fails. Neither of those is acceptable, and both come from the same cause — services calling each other directly. From there we build the idea up piece by piece: what a broker actually sits between, what a producer and a consumer really are, why you publish to an exchange instead of straight to a queue, and how bindings and routing keys decide where a message ends up. We go through all four exchange types, then queues as a buffer during a traffic spike, scaling out with multiple consumers, and the ordering guarantee you give up when you do. Then the part most tutorials rush — what happens when a consumer crashes mid-transaction: acknowledgements, redelivery, why your consumers have to be idempotent, retries, dead letter queues, durable queues, publisher confirms and quorum queues. We finish with an honest comparison against Apache Kafka and a straight answer on which one to reach for. CHAPTERS 0:00​ The transfer that feels instant 0:13​ What still has to happen after you tap Transfer 0:34​ The problem RabbitMQ was built to solve 0:54​ One transfer, step by step 1:11​ Producers, consumers and the broker 1:21​ Exchanges, bindings and routing keys 1:43​ Direct, fanout, topic and headers exchanges 2:15​ Queues, buffering and traffic spikes 2:34​ Scaling out with multiple consumers 2:52​ A consumer crashes: acks, redelivery, idempotency 3:23​ Retries and dead letter queues 3:41​ Durability, publisher confirms and quorum queues 4:07​ RabbitMQ vs Apache Kafka 4:40​ When to use which 4:58​ Recap WHO THIS IS FOR Developers who keep seeing RabbitMQ in architecture diagrams and want the idea to actually click, backend engineers about to put a queue in front of work that currently makes every request wait, and anyone interviewing for a role where asynchronous messaging or system design comes up. #rabbitmq​ #messagequeue​ #systemdesign​ #backend​ #microservices​ ​

About