_index.md

title	date	lastmod	keywords	toc	draft	reviewed
Registry and Discovery	2017-11-06 17:45:44 -0500	2018-05-15		false	false	true

Services typically need to call one another. In monolithic applications, services invoke one another through language-level methods or procedure calls. In a traditionally distributed system deployment, services run at fixed, well-known locations (hosts and ports), so they can easily call one another using HTTP/REST or some RPC mechanism. However, a modern microservice-based application typically runs in a virtualized or containerized environments where the number of instances of a service and their locations (IP and port) changes dynamically.

This tutorial shows how to use the service registry and discovery feature of the light platform to discover services and invoke them with the client module.

• Introduction and Code Generation

• Static Configuration

• Dynamic Service Discovery with Direct Registry

• Multiple Instances of the same Service

• Consul Service Registry and Discovery

• Multiple Instances with Environment Segregation

• Securing Consul with acl_token

• Service Discovery with Docker Containers

• Kubernetes

• OpenShift

• Router Assisted Service Discovery

• Consul Production with TLS

• External Config

• Consul HTTP Health Check

• Enable Security

• External Config

• Docker-compose and Consul Production

• OpenTracing with Jaeger