This is an overview for some of the different backends used by Spring Cloud Config:
- Standalone GIT: This is the classic Spring Cloud Config configuration where there is a service that takes care of all the configuration for the different apps and is deployed independently.
- Embedded GIT: Example of how you can embed the Spring Cloud Config server in your application. This helps from an infrastructure point of view as well as from a resiliency point of view.
- Zookeeper: Show how to integrate with Zookeeper as your configuration source.
- Consul: Very similar to the previous example, but using Consul instead.
- Vault: Integrates your application with Vault which is a very good way of managing secrets.
- Composite: It also provides a sample which uses a few backends at the same time.
A docker-compose.yml file is provided to make it easier to load up the infrastructure. When running docker-compose up
you'll get:
- Zookeeper Exhibitor running on http://localhost:8400/exhibitor/v1/ui/index.html.
- Consul running on http://localhost:8500/
- Vault running on http://localhost:8200/
- A nice Vault UI running on http://localhost:8300/
- RabbitMQ running on port 5672 to use for automatic updates for the standalone example.