Skip to content

Latest commit

 

History

History
22 lines (17 loc) · 1.35 KB

README.md

File metadata and controls

22 lines (17 loc) · 1.35 KB

Discovery Service

We use Netflix Eureka as a service registry. It provides a REST API for service registration and querying.

A service registry is useful because it enables client-side load-balancing and decouples service providers from consumers without the need for DNS. Each service has to register to the service registry. To be informed about the presence of a client, they have to send a heartbeat signal to the registry. Each client can query the service registry, which maintains a list of all available service instances. After the client retrieves the list of available service instances, he uses a load balancing algorithm to select available instance. Clients also have an in-memory cache of Eureka registrations (so they do not have to go to the registry for every request to a service).

Running the Discovery Service

The best way to run the service is with IDE like IntelliJ IDEA or Eclipse. Alternatively, after you build the service, you can run it with the following command:

~ java -jar infrastructure/discovery/build/libs/discovery.jar

Optional profiles:

  1. elk - to enable ELK logging.
  2. distributed-tracing - to enable distributed tracing with Sleuth and Zipking.
  3. docker - used when the service is run with docker.