Welcome back to TechTalks with Manoj — the show where we take the problems everyone pretends to understand, strip out the jargon, and explain what actually matters when you’re trying to keep microservices from behaving like a pack of unsupervised toddlers in production.

Today, we’re diving into a topic that quietly makes or breaks every distributed system out there: Service Discovery.

Now, most teams don’t think about service discovery until things catch fire.You know the moment — some service suddenly can’t find another service, requests start timing out, dashboards go red, and everyone starts asking, “Who changed the IP address?” Spoiler: nobody did. Your architecture just outgrew the idea of static endpoints.

In this episode, we’re unpacking the part of microservices that rarely gets spotlighted, but absolutely determines whether your system scales elegantly…or collapses at the first sign of traffic.

We’ll break down:

• Why static IPs died the moment containers became mainstream — and why pretending otherwise is a career-limiting move.• Client-side vs. server-side discovery — and why stuffing discovery logic inside every service is a great way to create long-term maintenance debt.• How Kubernetes, DNS, and the humble ClusterIP quietly solved 80% of discovery challenges.• Why Service Mesh took things to the next level with sidecars, mTLS, and traffic intelligence that feels like magic — until you deploy it.• The real differences between Consul, Etcd, and Eureka — and how their consistency models shape your system’s behavior under failure.• And finally, what it actually looks like to implement service discovery cleanly in .NET — without hardcoding endpoints or shipping “temporary” config files that mysteriously live forever.

By the end of this episode, you’ll stop thinking of service discovery as plumbing, and start seeing it for what it truly is:the dynamic address book that keeps your microservices talking to each other — accurately, consistently, and without waking you up at 2 AM.

So if you’ve ever chased a failing service across shifting IPs…if you’ve ever watched Kubernetes reschedule pods faster than your logs can keep up…or if you’ve simply wondered why your system sometimes can’t find the thing it’s calling—

This episode is your map through the madness.

Let’s get into it. ⚙️

Thanks for reading! Subscribe for free to receive new posts and support my work.