Building Enterprise JavaScript Applications

Global configuration store

Oftentimes, as is the case with our services, environment variables need to be set before the service can run successfully. So far, we've specified the environment variables to use by using the docker run --env-file flag:

$ docker run --env-file ./.env --name hobnob -d -p 8080:8080 hobnob:0.1.0

However, when deploying services on a cluster, we no longer run each container manually—we let the scheduler and node-level tools do this for us. Furthermore, we need all our services to share the same environment variables. Therefore, the most obvious solution is to provide a Global Configuration Store that stores configuration that is to be shared among all of the nodes and services.