|
The DeploymentService is designed to help manage differences
in configurations between application deployments.
This service service allows configurations for
all environments and all instances within each environment to be stored
separately and chooses the right configuration at runtime for each
environment/instance. This allows all configurations to reside
under source control and alleviates the error prone task of maintaining
manually modified files on each deployment.
For example, a project may have a development team of 15 engineers,
2 test instances, 2 staging instances and
4 instances in production. Each instance within each environment must
be configured with its host and port. Without this service, each
of the 23 deployed instances would have a configuration file that
would be manually modified to contain the correct data. Historically,
this kind of process is error prone, difficult to manage, and a
constant headache for project teams.
This service allows all 23 configurations to reside
in the source code repository and managed as code.
|