← Back to microservices patterns mapops
🏃
Microservices Pattern
Health Check / Readiness Probe
Expose endpoints that tell orchestrators whether the service is alive and ready.
Detailed Description
Liveness and readiness answer different questions. A service can be alive but not ready.
Readiness should check critical dependencies needed to serve traffic.
Visual Diagram
Liveness: should restart? Readiness: should receive traffic? Startup: finished booting?
Tradeoffs
Pros
Auto recovery, no traffic to unhealthy pods
Cons
Bad probes can cause false restarts
Examples: Kubernetes livenessProbe, readinessProbe, Consul health