As soon as your application and especially your application load gets bigger, you might want to share the load between several hosts. So you would setup several Play application nodes, all having the same configuration file, which is easily possible with Play. However, you would have to restart all application nodes, when you change one parameter. This is useful when you change something fundamental, like your database configuration. However there are cases where it is not useful to have a downtime of your application. This is where the principle of a centralised configuration service becomes useful. This recipe shows a simple example of how to implement such a service.
You can find the source code of this example in the examples/chapter7/configuration-service
directory.