8.2.5 Manual Service Discovery Configuration

If you do not wish to involve a service discovery server like Consul or you interact with a third-party service that cannot register with Consul you can instead manually configure services that are available via Service discovery.

To do this, use the micronaut.http.services setting. For example:

Manually configuring services

  1. micronaut:
  2.   http:
  3.     services:
  4.       foo:
  5.         urls:
  6.           - http://foo1
  7.           - http://foo2

You can then inject a client with @Client("foo") and it will use the above configuration to load balance between the two configured servers.

When using @Client with service discovery, the service id must be specified in the annotation in kebab-case. The configuration in the example above however can be in camel case.
You can override this configuration in production by specifying an environment variable such as MICRONAUT_HTTP_SERVICES_FOO_URLS=http://prod1,http://prod2

Note that by default no health checking will happen to assert that the referenced services are operational. You can alter that by enabling health checking and optionally specifying a health check path (the default is /health):

Enabling Health Checking

  1. micronaut:
  2.   http:
  3.     services:
  4.       foo:
  5.         ...
  6.         health-check: true (1)
  7.         health-check-interval: 15s (2)
  8.         health-check-uri: /health (3)
1Whether to health check the service
2The interval between checks
3The URI of the health check request

Micronaut starts a background thread to check the health status of the service and if any of the configured services respond with an error code, they are removed from the list of available services.