MicroSvcs_ConfigCenter-[TODO]
Last updated
Was this helpful?
Last updated
Was this helpful?
Static config files could not be changed dynamically. Need to be redeployed
Configuration exists in many different places (e.g. xml, properties, DB). Errorprone for livesites.
No security audit and version control
Cloud native requires immutable infrastructure and microservices. This type of continuous delivery requires the architecture of configuration center.
Access control and audit history
Gradual rollout
Management for different environments/clusters
Database/middleware/service connection string
Username, password, token, certificates
Application configuration: Request timeout, thread pool, queue, cache, connnection pool size, circuit breaker threshold, black-white list
Function on-off toggles: Blue green deployment, HA toggle
Business logic toggles:
Feature flag driven development
Pros:
Cons:
Trunk based development
Benefits:
Replanning
Config operations and open source comparison:
Server architecture:
Client architecture:
High availability architecture:
Appolo architecture: