apollo distributed configuration principles Center

Disclaimer: This article is a blogger original article, follow the CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source link and this statement.
This link: https://blog.csdn.net/Leon_Jinhai_Sun/article/details/102763666

 

https://github.com/ctripcorp/apollo

About Apollo Apollo

 

Apollo (Apollo) is a research and development department Ctrip framework for distributed configuration center, capable of centralized management applications in different environments, different cluster configuration, the configuration changes can be pushed to real-time application side, and have standardized permissions, process control and other features, applicable to micro-service configuration management scenarios.

Apollo Apollo Features

After you modify the user configuration and release Apollo, the client in real-time (one second) receive the latest configuration and notification to the application.

Unified management of different environments, different cluster configuration

 

All configuration concept has released version, which can easily support rollback configurations.

Configuration changes with immediate effect (heat release)

After the user to modify the configuration and the Apollo released, the client in real-time (one second) receive the latest configuration and notification to the application

Release management

All configuration has released version concept, which can be easily configured to support rollback

Gray release

It supports the configuration of the gray release, such as point after release, takes effect only on the part of application examples, and other observations again and again to all application instances after a period of time, no problem.

Rights management, post audit, operational audit

Application and configuration management has improved rights management mechanism, the management configuration is also divided into two aspects of editing and publishing, thereby reducing human error.

All operations have audit logs, you can easily track down the problem.

 

 

Guess you like

Origin blog.csdn.net/Leon_Jinhai_Sun/article/details/102763666