I am developing a web application that will contain quite a few hosts. I saw how external configuration stores were used in Java, for example, with Spring Cloud Config Server.
Are there any non-standard alternatives in .NET? I am currently looking at the MSDN external settings repository template , deploying it to order, and reusing part of the code from this page.
In fact, each node will have a source configuration file (JSON) containing, for example, the name of the node and the URL of the database, where it will find other configuration parameters. Then I will have a separate service that can be requested by other services to return configuration data. It also caches configuration data locally.
There are some problems with this:
- how well it works, i.e. configuration service may need to be scaled across multiple instances,
- configuration data must be cached, and even a distributed cache for all configuration services may be required to have a single view of the cached configuration data,
- it is an individual implementation that requires maintenance,
- how do configuration data change, for example, through the admin user interface with CRUD operations?
source
share