MicroSvcs_ConfigCenter-[TODO]

Configuration center

Motivation

  • 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.

Config operations and open source comparison [Todo]

Requirements on configuration center

  • Access control and audit history

  • Gradual rollout

  • Management for different environments/clusters

Configuration categories

Static configuration

  • Database/middleware/service connection string

  • Username, password, token, certificates

Dynamic configuration

  • 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:

Use case

Blue green deploymment

Graceful downgrade

DB migration

AB testing

Continuous delivery

Feature flag driven development

  • Pros:

  • Cons:

Trunk based development

Apollo Architecture (In Chinese)

Last updated