Backing service. The configuration service is a vital component of any microservices architecture. Based on the twelve-factor app methodology, configurations for your microservice applications should be stored in the environment and not in the project.
Backing service. An application to manage and monitor microservices
Backing service. Authorization server (OAUTH2) - for issuing tokens and authorize requests.
Eureka Server that works with springCloudVersion = 'Edgware.SR2'
The Crown Commercial Service's PPON ID Service, for Conclave/PPG.
Backing service. Netflix Eureka is a service registry. It provides a REST API for service instance registration management and for querying available instances. Netflix Ribbon is an IPC client that works with Eureka to load balance(client side) requests across the available service instances.
Backing service. Configuration for microservices
Licensing Service use Redis and distributes tokens accross microservices
Backing service. Implementation of an API gateway that is the single entry point for all clients. The API gateway handles requests in one of two ways. Some requests are simply proxied/routed to the appropriate service. It handles other requests by fanning out to multiple services.
Add a description, image, and links to the backing-service topic page so that developers can more easily learn about it.
To associate your repository with the backing-service topic, visit your repo's landing page and select "manage topics."