By default Spring Cloud Config uses git repositories as its backing store, so version history is more or less handled. You can also use file systems, Vault, JDB

By default Spring Cloud Config uses git repositories as its backing store, so version history is more or less handled. You can also use file systems, Vault, JDBC, Redis, AWS S3 and CredHub as backends out of the box[0]. You can also mix and match backends, so that (say) regular config goes into Git and secrets go into Vault or CredHub. It ought to be straightforward to add Config.ly as a backend, which would give you a pathway into a very large developer population (both Java+Spring and .NET via Steeltoe[1]). For GUI cases, Spring Cloud Azure[2] adds Azure App Configuration[3] as another backend. Disclosure: I work for VMware, which sponsors Spring development, but not on Spring. [0] https://cloud.spring.io/spring-cloud-config/reference/html/#_environment_repository https://cloud.spring.io/spring-cloud-config/reference/html/#... [1] https://steeltoe.io/app-configuration https://steeltoe.io/app-configuration [2] https://spring.io/projects/spring-cloud-azure https://spring.io/projects/spring-cloud-azure [3] https://docs.microsoft.com/en-us/azure/azure-app-configuration/ https://docs.microsoft.com/en-us/azure/azure-app-configurati...