Scaling out Content Delivery Server Roles to separate machines
Each of the Server Roles can be installed on a separate machine to improve Content Delivery performance. Especially the Content Deployer, which typically carries most of the performance burden, is best installed on a separate machine. In such a scaled-out scenario, if you install a standalone microservice on its own machine, ensure that its PowerShell installation script does not include a dependency on the Discovery Service.
About this task
By default, when any standalone microservice (other than the Discovery Service) is started, it first checks if the Discovery Service is running. If the Discovery Service is not running, it runs the Discovery Service and then starts itself.
In a scaled-out scenario, the Discovery Service does not run on the same machine as the standalone microservice, and so the microservice's dependency on it must be explicitly switched off.