ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Hardcoded service IPs break under autoscaling. Consul replaces them with a self-registering catalog and DNS-based discovery—if you tune health checks and TTLs correctly.
Ephemeral services behind NAT need discovery that fails fast without flapping. This guide compares Consul's pull-based HTTP/TCP checks and push-based TTL checks, then shows how to validate that only healthy instances answer DNS and HTTP queries.
When a Consul‑registered service shows a critical status even though its process is running, the issue is almost always a connectivity or configuration problem. This guide walks through the most common root causes, shows how to verify each, and lists concrete fixes and escalation steps.
Dropwizard's built-in HealthCheck system gives services a standard /healthcheck view of dependency readiness without custom endpoints, plus the trade-offs to plan for.
A diagnostic guide to gRPC health check failures: matching symptoms like UNAVAILABLE errors and false NOT_SERVING statuses to transport, naming, and deadline causes, with ordered checks and fixes.
Learn how to implement and register custom HealthChecks in Dropwizard to monitor database and API dependencies via the admin port, preventing traffic from hitting unhealthy instances.
A diagnostic guide for Consul operators: why dead service instances linger in the catalog, how to pinpoint the cause (check misconfiguration, missing deregistration, ungraceful node loss, anti‑entropy failure), and step‑by‑step fixes with verification methods.
An architecture note for running Postman Monitors in production: the smallest viable design, secret-handling boundaries, operational checks, and the failure modes that should each trigger a distinct alert.
Register a health-checked service, resolve it over Consul's DNS interface on port 8600, route .consul queries from the host resolver, and verify that failing instances drop out of answers.
consul
dropwizard
java