Consul Service Discovery: DNS vs HTTP API Decision Guide
Guide for choosing between Consul DNS and HTTP API for service discovery, comparing caching, metadata, load balancing, and practical validation steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Guide for choosing between Consul DNS and HTTP API for service discovery, comparing caching, metadata, load balancing, and practical validation steps.
Learn how to choose between Round Robin, Least Request, and Maglev load balancing policies in Envoy Proxy to optimize for latency, cache hits, and resource distribution.
Socket.IO rooms broadcast only within one Node process. Learn when to add the Redis adapter and verify cross-node delivery.
Architecture note for a minimal Apache 2.4 reverse proxy that terminates TLS, load-balances HTTP backends with health checks, preserves client IP, and supports graceful draining — plus the triggers that force a redesign.
Learn how to implement NGINX upstream groups to distribute traffic across multiple backend servers using least_conn and passive health checks.
Scaling a Moleculer service works without client-side changes. The Service Broker registers its actions automatically, making them discoverable and load balancing request-response calls across instances using Round Robin. Transport-agnostic communication works over TCP, Redis, or NATS.
The default PickFirst policy silently selects one server and ignores the rest—causing uneven load and hidden failure risks in multi-instance gRPC deployments.
Learn how to turn on gRPC Java’s built‑in round‑robin resolver, wire a ManagedChannel to multiple backends, and avoid common pitfalls.
Use NGINX upstream and proxy_pass to distribute traffic across multiple backend servers, with passive health checks and header forwarding.