liveBook · Manning

Health check endpoint

As explained in Microservices Patterns, Second Edition

An endpoint that can be invoked to determine whether a service instance is healthy and available to handle requests.

A health check endpoint is an API URL that a service registry can invoke periodically to verify that a service instance is healthy and available to handle requests. It also contributes to service observability. section 7.6.2 section 8.2.5

Within service discovery, the endpoint:

  • Can be supplied when a service instance registers its network location with the registry. section 8.2.5
  • Lets the registry check instance health periodically; a separate heartbeat API may be required to keep the registration from expiring. section 8.2.5

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the endpoint's purpose and registry invocation, but gives no implementation, response format, or health criteria.
Examples
Uses a service instance URL that a registry periodically invokes to verify health and request availability.
What it assumes
Assumes service instances register network locations with a service registry and situates health checks within that discovery flow.
What you can do after
Operate service registration by exposing a URL that the registry can invoke periodically to check instance health and availability.
How it connects
Connects service discovery with service registries, self-registration, and heartbeat APIs.

Also explained in

Compare how 7 books explain health check endpoint →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.