Its correct to create a unique appsettings class to manage many appsettings of many microservices?

Question

Just as title my doubt is related to dont break pattern of microservice.

I have some microservices with their own appsettings.json and a class for each one where i am going to load these.

The class essentially contains settings for the database and other configurations.

It makes sense to unify the appsettings class for all microservices, so that it is used in each microservice where I load the specific values of appsettings.json, in this case I could have properties that remain empty as not all microservices have in the appsettings.json the same settings.

I don't know if this can be contrary to the microservices pattern.

What do you think?
thanks

Answer 1

One of the key goals of micro services is independent deployment. That is you are free to change and redeploy a micro service with out requiring any other deployments. So you need to be careful with shared code.

Rather than one master setting class, how about individual config class for each component that maps to a section.

note: also not clear why micro services would have a lot of common settings. they are supposed to be independent.

Answer 2

Many thanks ,it my thought but im not was sure