Eliminating Hard-Coded IPs with Consul Service Discovery
Stop relying on static IP addresses in your microservices. Learn how Consul uses a service registry and health checks to provide dynamic DNS-based discovery.
Loading…
ReadMeFeed / Community knowledge
#service-discovery
Real questions. Useful conversations. Find the people who know your stack.
consulImplementing Service Routing with Consul Prepared Queries
Learn how to use Consul Prepared Queries to create stable, named service filters for DNS and HTTP, reducing application complexity and managing failover targets.
Consul Anti-Entropy Synchronization and Local State Divergence
Consul uses a distributed architecture where health checks are executed by local agents to minimize server load. While the gossip protocol (Serf) manages cluster membership, the synchronization of local agent state with the server cluster relies on anti-entropy mechanisms to ensure eventual consistency. In environments with rapid service flapping—where a ser
Nomad built-in DNS TTL and cache invalidation after allocation reschedule
Nomad provides an optional built-in DNS server for service and allocation name resolution under the nomad domain, with records derived from the catalog and allocation state. API and inter-node RPC can be secured with TLS where server certificates must contain SANs matching advertised addresses and clients validate against a configured CA. DNS queries are ser
Critical health state propagation delay in Consul DNS
When migrating a small application to new infrastructure using Consul for service discovery, the goal is to achieve zero downtime by leveraging health checks to steer traffic. In this architecture, the Consul DNS interface is used to resolve healthy service instances. A potential conflict arises when a service instance is marked as critical . While the Consu
DNS Strategy: TLS Certificate Validation Limits in Moleculer
Goal Determine how Moleculer’s DNS service discovery strategy handles TLS certificate validation when connecting to discovered services, and whether a unified policy can be enforced. Constraints The framework’s DNS strategy resolves SRV records but delegates connection security to individual transporters (e.g., NATS, MQTT, Redis). Transporter implementations