Chiman Jain
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
🌐 dev.toSource
From Dev.to - go: 🚀 Stop Chasing Small Docker Images: What Actually Matters for Go in Production
🌐 dev.toSource
From Dev.to - grpc: Stop Fighting Annotations: Why Kubernetes Gateway API is Replacing Ingress
🌐 dev.toSource
When building APIs in Go, it’s easy to get caught up in the rush to ship. You create an elegant endpoint, document it, and call it a day. But as your service evolves and your user base grows, what once seemed like a simple, clean API can quickly turn into a maintenance nightmare.
🌐 dev.toSource
I’ve been writing Go for over 8 years now, and like many developers, I started with high hopes, clean code, and a naive understanding of what it takes to build scalable, maintainable systems. Over the years, I’ve written more Go code than I’d care to admit, and like many seasoned
🌐 dev.toSource
In modern cloud-native environments, especially those leveraging Kubernetes, configuration management becomes a critical part of maintaining scalable, resilient applications. Kubernetes provides several ways to handle configurations, but knowing how to reload configurations dynam
🌐 dev.toSource
When building high-performance microservices in Go, one question inevitably comes up: Should you use REST or gRPC? This isn’t just an architectural debate it directly impacts latency, throughput, infrastructure cost, and scalability. In this post, we’ll break down REST vs gRPC pe