This is a request for more documentation around best practices using spring cloud config server

The Embedding the Config Server documentation states:

The Config Server runs best as a standalone application

It would be great if there was more documentation around the pros and cons of running an embedded server as against a centralized configuration server.

Within our organization we are debating against these approaches and it feels like we were missing something in the documentation that supports either cause.

Here is what I could come up with:

Assumptions: We are using git as the datastore for the app configurations

Embedded server:
Pros:
No need to standup a new server

Cons:
Each application will now have to

1. store git credentials
2. store encryption keys if encryption mode is turned on
3. have ssh configuration to communicate with git repository, assuming ssh is the mode of authentication

Centralized server:
Pros:
Centralized server to:

1. serve out configurations
2. encrypt information
3. git credentials

Cons:

1. Single point of failure