Daksh Paleria

2.1K posts

Daksh Paleria banner
Daksh Paleria

Daksh Paleria

@dakshp07

Engineering @letsblinkit | SoB'22 @bcoin | GSoC'21 @cdli_news | VIT'23

Bengaluru South, India Katılım Mayıs 2021
1.3K Takip Edilen541 Takipçiler
Daksh Paleria retweetledi
Paul Bohm
Paul Bohm@paulbohm·
If your startup does not have a UUID microservice you’re ngmi
Paul Bohm tweet media
English
180
255
6.4K
622.4K
Daksh Paleria retweetledi
spidey
spidey@lochan_twt·
The day a blind man sees. The first thing he throws away is the stick that has helped him all his life
spidey tweet media
English
663
4.4K
60.6K
2.6M
Daksh Paleria retweetledi
Arpit Bhayani
Arpit Bhayani@arpit_bhayani·
We no longer have skill issues, we have skill-md issues.
English
56
175
2.9K
68.4K
Daksh Paleria retweetledi
Hernan Cortes
Hernan Cortes@CyberPunkCortes·
Does anyone know why the Danish Frogman Corps uniform had to go so hard?
Hernan Cortes tweet mediaHernan Cortes tweet mediaHernan Cortes tweet media
English
354
2.6K
49.7K
2.3M
Daksh Paleria retweetledi
culture jpeg
culture jpeg@culturejpg·
FBI agent pulling out MP7 from his backpack during the shooting at the White House Correspondents Dinner (2026)
culture jpeg tweet mediaculture jpeg tweet mediaculture jpeg tweet mediaculture jpeg tweet media
English
22
217
4.2K
576K
Daksh Paleria retweetledi
Vatsalya
Vatsalya@vatsalyatandon·
come to toit bro. i just went to mezcalitas. it's next to smash guys bro. check district bro. we are at toit bro. have you been to soka. location on whatsapp bro. saw it on a reel bro. don't need couple entry. are you at double bar. come to WIP bro. check the group bro.
English
13
38
935
36.2K
Daksh Paleria retweetledi
Puneet Patwari
Puneet Patwari@system_monarch·
Message Queues & Event-Driven Patterns are the backbone of every scalable modern system - Netflix, Uber, and Atlassian all run on them. Most engineers know the basics (“just throw a queue in there”), but interviewers destroy you with the deep follow-ups: “How do you guarantee exactly-once processing when a Kafka broker dies mid-replay?” “How do you handle poison messages without crashing your entire consumer fleet?” “What happens to your Sagas during a partial failure at 50k events/sec?” These 20 must-know Message Queues & Event-Driven Patterns take you from high-level overview to production-grade depth that actually ships reliably at scale. Save this thread. Read till the end.
English
5
63
605
53.4K
Daksh Paleria retweetledi
Kinki Muniain
Kinki Muniain@Kinki_muniain·
La liga de Groenlandia está a otro nivel,
Kinki Muniain tweet mediaKinki Muniain tweet media
Español
378
6.3K
85.3K
3.5M
Daksh Paleria retweetledi
Shvvposts
Shvvposts@Shivender_Abrol·
Life can be bad
Shvvposts tweet media
English
49
544
18.2K
405.1K
Daksh Paleria retweetledi
Jaydeep
Jaydeep@_jaydeepkarale·
Kubernetes Service Discovery Clearly Explained !!! Every Pod in Kubernetes gets its own IP. Sounds great… until it breaks your system. In a Deployment, you don’t run just one Pod. You run multiple replicas: pod-1 → 10.0.0.1 pod-2 → 10.0.0.2 pod-3 → 10.0.0.3 Each Pod has its own IP. So far, so good. Now imagine another service wants to call this app. What should it use? 10.0.0.1? 10.0.0.2? 10.0.0.3? There’s no single stable address. Already a problem. Now it gets worse. Pods are ephemeral. If a Pod dies: it is deleted a new Pod is created with a completely NEW IP Example: old pod → 10.0.0.2 ❌ new pod → 10.0.0.9 ✅ Your system is now pointing to a dead IP. So the real problem is: 👉 Pod IPs are dynamic 👉 Clients need a stable way to connect Without that, service-to-service communication is unreliable. This is exactly what Kubernetes Services solve. Instead of pointing to Pods directly, you create a Service. And here’s the key idea: 👉 You don’t connect to Pods 👉 You connect to a logical group of Pods How does Kubernetes know which Pods belong to that group? Using: labels & selectors Pods are tagged with labels: labels: app: user-service The Service defines a selector: selector: app: user-service That’s it. This simple mapping connects them. Now Kubernetes keeps track of: “All Pods with label app=user-service belong to this Service” Even if Pods die or restart or scale up/down, The mapping is always updated. And the Service gives you a stable entry point: a fixed IP (ClusterIP) a DNS name So clients just call: 👉 user-service Not individual Pods. Behind the scenes Service finds matching Pods via labels traffic is routed to one of them, dead Pods are automatically removed, new Pods are automatically added No manual updates. So the transformation is: ❌ Before: Call fragile Pod IPs that keep changing ✅ After: Call a stable Service that tracks Pods dynamically If you remember one thing: Kubernetes doesn’t make Pods stable. It makes access to Pods stable. That’s the real purpose of a Service. Not just load balancing. But solving the “changing IP” problem elegantly.
Jaydeep tweet media
English
18
99
464
25.1K
Daksh Paleria retweetledi
Wren
Wren@wrendom·
The blue shirts that GT players wore on Gujarat Day celebrations aren’t just your regular shirts. They’re Tangaliya (તાગળિયાં), a 700-year-old handloom craft from Gujarat. Handwoven, GI-tagged, rooted in heritage. Even Brad Pitt wore it in the movie, F1 (2025). From Gujarat’s Surendranagar to Hollywood and now in IPL. Aava de 💙⚡
Wren tweet mediaWren tweet mediaWren tweet media
Newr@KaiCobra_

We might not have a Gujarati player in GT but we've got Sai Sudharsan omg 🎀😭

English
40
207
2.3K
315.8K
Daksh Paleria retweetledi
Katie Chiou
Katie Chiou@katiewav·
crazy how this might still be the best tech logo of all time
Katie Chiou tweet media
English
222
1.1K
30.6K
1.6M
Daksh Paleria retweetledi
Aaron
Aaron@aaronp613·
Apple accidentally left Claude.md files in today's Apple Support app update (v5.13)
Aaron tweet mediaAaron tweet media
English
283
1K
13.6K
2.6M
Daksh Paleria retweetledi
Anish Moonka
Anish Moonka@anishmoonka·
Rafa Nadal won the 2022 French Open with his left foot completely numb. His doctor had been injecting anesthetic into the nerves before every match, for two solid weeks. After one of those matches he couldn’t walk, and his father had to carry him to the hotel. That was his 14th French Open title. No tennis player, male or female, has ever won the same tournament that many times. His career record at the French Open was 112 wins, 4 losses. That 96.6% win rate is the highest by any player at any major in history. Only three men ever beat him in Paris: Söderling in 2009, Djokovic twice, and Alexander Zverev in his final appearance in 2024. The forehand that powered all of it spins faster than a washing machine on spin cycle. About 3,200 rotations per minute on average, peaking at 5,000. Federer’s spins at 2,500. Sampras and Agassi were at 1,800. Nadal’s ball spins about 80 times in the time it takes to cross the court. The condition in his foot is called Müller-Weiss syndrome. It is a rare disease where a small bone in the middle of the foot slowly collapses. He has had it since 2005. There’s no cure. He once said he doesn’t remember what playing without pain feels like. He retired last November in tears, after Spain lost a Davis Cup quarter-final to the Netherlands. Across 23 years he won 22 Grand Slams, 92 tour titles, and 1,080 of his 1,308 singles matches. He held the world number one ranking for 209 weeks and earned $134.9 million in prize money. The Netflix series drops May 29, in the middle of this year’s French Open. He turns 40 five days later. The tagline is “A Life Beyond Limits.” That was the job description of a tennis career he played, for years, on a foot doctors said could not hold up.
Netflix@netflix

"To reach the top, you have to go near the limit." - @RafaelNadal The documentary series Rafa premieres May 29.

English
49
1.1K
7.6K
968.7K
Daksh Paleria retweetledi
cinesthetic.
cinesthetic.@TheCinesthetic·
Christopher Nolan's hand drawn map for the plot of INCEPTION (2010)
cinesthetic. tweet mediacinesthetic. tweet media
English
23
1K
10.1K
647.9K
Daksh Paleria retweetledi
Y Combinator
Y Combinator@ycombinator·
AI has stopped being a feature and started being the foundation. We're excited about a new wave of startups rebuilding software, services, and silicon— and pushing AI into the physical world. ycombinator.com/rfs
Y Combinator tweet media
English
208
958
8.9K
4.3M