Harish | BuildInJava @BuildInJava

12 yrs building scalable & distributed systems. Java • Spring Boot • Microservices. Refining performance, design & scale. Follow - let’s grow 🚀 Bangalore Joined February 2026

Tweets

11
Followers

13
Following

132
Likes

27

Harish | BuildInJava @BuildInJava

2 months ago

@ashoKumar89 Congrats Ashok! Always good content.

1 0 1 687 0

View Details

Ashok Sahoo @ashoKumar89

2 months ago

Hit 5M impressions 🚀 Still ~200 followers away from 500 verified. If you’ve been getting value from my posts on backend, systems, and real-world dev stuff follow along. Let’s grow together.

50 17 442 334K 385

View Details

‎Wojak Codes @wojakcodes

a year ago

"Use the weekend to build the life you want, not to escape the life you have."

14 76 798 42K 156

View Details

Harish | BuildInJava @BuildInJava

3 months ago

@grok @m_im_ha @DeRonin_ Yes reply now

1 0 0 25 0

View Details

Kubernetes doesn't fail randomly, It fails in patterns. If your debugging strategy is just: kubectl logs kubectl describe pod …you're probably missing the real problem. Production failures in Kubernetes usually follow predictable paths. Think of it like a failure map. When something breaks, the issue is usually hiding in one of these layers: 1. Image layer Wrong image tag, private registry auth, or ImagePullBackOff. 2. Application layer App crashes -> CrashLoopBackOff -> container restart loops. 3. Configuration layer Broken ConfigMaps, Secrets, env variables. 4. Networking layer Service selectors mismatch, DNS failures, CNI issues. 5. Scheduling layer Insufficient CPU/memory -> Pod stuck in Pending. 6. Cluster layer Node NotReady, kubelet crash, control plane issues. Most engineers jump straight to logs. But real debugging starts with identifying which layer failed first. That’s how experienced SREs troubleshoot production outages. If you run Kubernetes in production, this failure map is gold. Comment “map” and I’ll send you the full article. #DevOps #Cloud #Kubernetes #SRE #Infrathrone

13 8 26 2K 25

View Details

Harish | BuildInJava @BuildInJava

3 months ago

@ashoKumar89 @__karnati 4. Put the developer on PIP

0 0 1 271 0

View Details

Harish | BuildInJava @BuildInJava

3 months ago

Streams are lazy. Unless there's a terminal operation, a stream won't execute.

Javarevisited @javarevisited

3 months ago

Java Stream Interview ☕ What happens here? Stream<Integer> stream = Stream.of(1,2,3); stream.map(x -> x * 2); Nothing printed. Why?

10 4 54 13K 31

0 0 1 20 0

View Details

Harish | BuildInJava @BuildInJava

3 months ago

Always you String.equals() to compare strings. Even better, compare with the constant like: "ADMIN".equals(role) This doesn't require you to do an additional null check.