Configuration and Registry

EdgeX uses a new microservice, Core Keeper, for Configuration Provider and Service Registry functions. Core Keeper integrates PostgreSQL for data persistence and leverages EdgeX modules go-mod-configuration and go-mod-registry to implement these services within the EdgeX architecture.

Configuration Management

For current Configuration Management, refer to the Core Keeper API documentation.

Service Registry

For detailed API documentation on Core Keeper's service registry, refer to the Core Keeper API documentation.

Service Registration

When each microservice starts up, it connects to Core Keeper to register its endpoint details, including microservice ID, address, port, and health-check methods. Other microservices can then discover its URL through Core Keeper, which also monitors health status. API details for registration are provided in the Core Keeper API documentation.

Service Deregistration

Before shutting down, microservices must deregister from Core Keeper. The deregistration API is described in the Core Keeper API documentation.

Service Discovery

The Service Discovery feature enables client microservices to query endpoint information for specific microservices by their ID or to list all available services registered in Core Keeper. Refer to the Core Keeper API documentation.

Health Checking

Health checking ensures only healthy services are used. Core Keeper offers HTTP + Interval as the health checking method, see the Core Keeper API documentation.

Health checks should be established during service registration, as detailed in the Service Registration section.