Microservice file configuration

1 Pain points based on local file configuration

   ① Modifying the local configuration file requires restarting the service

   ② viper can monitor changes in local configuration files and modify the value of variables in memory, which seems to meet the requirements   

    Pain points If there are too many instances, manual modification is very likely to make mistakes. Many services rely on a configuration. Operation and maintenance can write scripts to modify in batches

    If there is a problem, the operation and maintenance do not want to take the blame

   ③ The framework and configuration files used in the multi-language development instance are different

Solution:

   Configuration Center Independent Service

   Each instance reads configuration from the configuration center   

   With permission control, configuration rollback, real-time push, environment isolation and other functions, it solves the configuration problem of microservices

Tool selection

nacos already supports grayscale publishing

 

 

Guess you like

Origin blog.csdn.net/pzl_pzl/article/details/131353787
Recommended