Which combination of networking components is best to ensure service discovery, secure communication, and load balancing?
hard📝 Trade-off Q15 of 15
Microservices - Orchestration with Kubernetes
You are designing a microservices system where services must communicate securely and efficiently. Which combination of networking components is best to ensure service discovery, secure communication, and load balancing?
AService registry for discovery, TLS for security, and API gateway for load balancing
BStatic IPs for discovery, HTTP for communication, and DNS for load balancing
CManual config files for discovery, plain TCP sockets, and round-robin DNS
DNo discovery needed, use UDP for speed, and client-side load balancing
Step-by-Step Solution
Solution:
Step 1: Identify components for service discovery
A service registry dynamically tracks services, enabling discovery.
Step 2: Choose secure communication and load balancing
TLS encrypts data for security; API gateway can handle load balancing efficiently.
Step 3: Evaluate other options
Static IPs and manual configs lack flexibility; plain TCP and UDP lack security; DNS load balancing is limited.
Final Answer:
Service registry for discovery, TLS for security, and API gateway for load balancing -> Option A
Quick Check:
Discovery + TLS + API gateway = secure scalable system [OK]
Quick Trick:Combine registry, TLS, and gateway for best networking [OK]
Common Mistakes:
MISTAKES
Using static IPs instead of dynamic discovery
Ignoring encryption needs
Relying solely on DNS for load balancing
Master "Orchestration with Kubernetes" in Microservices
9 interactive learning modes - each teaches the same concept differently
