Service Discovery
DNS, Consul, K8s services, client-side discovery.
Theory
Service discovery lets clients locate healthy instances of a service without hardcoded IPs — critical when containers and VMs are ephemeral. Registries track instance metadata, health status, and optional load-balancing hints.
Client-side discovery (Eureka, Consul): the client queries the registry and picks an instance. Server-side discovery (Kubernetes Services, cloud LBs): a proxy resolves and routes on behalf of clients — simpler client code.
Health checks continuously register and deregister instances. DNS SRV records offer simple discovery but TTL limits failover speed. Service meshes integrate discovery with mTLS, retries, and traffic policies at the data plane.
Production rollouts require idempotent automation, peer review, staged apply, and documented rollback — treat changes as production code.
Interviewers want STAR stories linking Service Discovery to measurable outcomes: fewer outages, faster deploys, lower cost, or reduced toil.
Architecture Diagram
Users / clients
|
Service Discovery
|
Core services
|
Data + observabilityExamples
# Service Discovery
# DNS, Consul, K8s services, client-side discovery.
# Validate in staging before production rollout.Interview Questions
What problem does Service Discovery solve?
It addresses the core use case described in production architecture — map features to reliability, scale, or velocity outcomes.
Key components of Service Discovery?
Identify inputs, outputs, control plane, data plane, and failure domains — interviewers want structured decomposition.
Common production pitfalls?
Misconfiguration, missing observability, no rollback path, and scaling bottlenecks under peak load.
How do you test changes safely?
Staging parity, canary/gradual rollout, automated health checks, and documented rollback.
Metrics to prove success?
Error rate, latency percentiles, throughput, cost, and toil reduction — pick one primary SLO.
Beginner vs advanced concern?
Beginners focus on setup; advanced teams focus on blast radius, security boundaries, and operability at 10× scale.
Best Practices
- Treat Service Discovery config as code with review and CI validation.
- Define SLOs and dashboards before production cutover.
- Document rollback and ownership for on-call.
- Use least privilege for credentials.
Common Mistakes
- Adopting Service Discovery without measurable success criteria.
- No staging environment mirroring production constraints.
- Missing rollback path during incidents.
- Undocumented on-call expectations.
Trade-off Analysis
Service Discovery improves dns, consul, k8s services, client-side discovery. but adds operational and cognitive complexity — justify with load and team size.
Favor simplicity until metrics (p99 latency, error rate, cost) prove the pattern necessary.
Every redundancy layer trades capital/operational cost for availability — align with explicit SLO targets.
Document accepted inconsistency windows and recovery behavior before production cutover.
Cheat Sheet
Practical Exercises
Stand up Service Discovery locally or in free tier; document commands and failure recovery.
Introduce misconfiguration; practice detection and rollback under time limit.