Hands-On Microservices with Kubernetes

Remote configuration store

One of the options for dynamic configuration is a remote configuration store. All service instances can periodically query the configuration store, check whether the configuration has changed, and read the new configuration when it does. Possible options include the following:

• Relational databases (Postgres, MySQL)
• Key–value stores (Etcd, Redis)
• Shared filesystems (NFS, EFS)

In general, if all/most of your services already work with a particular type of store, it is often simpler to put your dynamic configuration there. An anti-pattern is to store the configuration in the same store as the service-persistent store. The problem here is that the configuration will be spread across multiple data stores, and some ...