A method of reallocating an application component from a faulty data-center resource to a non-faulty data-center resource, wherein the faulty data-center resource is included in a network of a plurality of data-center resources, the method comprising: identifying by a resource-status background monitor the faulty data-center resource on which the application component is deployed; determining by a group-health-dependent disabler a ratio of data-center resources that are faulty among a group of data-center resources, wherein, when the ratio exceeds a threshold ratio, the resource-status background monitor is disabled; generating a service-healing task instructing that the application component is to be transferred from the faulty data-center resource, wherein, when the ratio exceeds a threshold ratio, the service-healing task is not generated and wherein further a history is maintained that includes a number of occasions on which the application component is reallocated in a given period of time, and wherein, when the number exceeds a threshold number, the service-healing task is not generated; executing, if the service-healing task is generated a component-relocation background monitor that processes the service-healing task and that identifies the non-faulty data-center resource available to receive the application component; generating, if the service-healing task is generated a rolling-upgrade task instructing that the application component is to be transferred to the non-faulty data-center resource; and executing, if the service-healing task is generated a rolling-upgrade background monitor that processes the rolling-upgrade task and that reallocates the application component to the non-faulty data-center resource. identifying by a resource-status background monitor the faulty data-center resource on which the application component is deployed; determining by a group-health-dependent disabler a ratio of data-center resources that are faulty among a group of data-center resources, wherein, when the ratio exceeds a threshold ratio, the resource-status background monitor is disabled; generating a service-healing task instructing that the application component is to be transferred from the faulty data-center resource, wherein, when the ratio exceeds a threshold ratio, the service-healing task is not generated and wherein further a history is maintained that includes a number of occasions on which the application component is reallocated in a given period of time, and wherein, when the number exceeds a threshold number, the service-healing task is not generated; executing, if the service-healing task is generated a component-relocation background monitor that processes the service-healing task and that identifies the non-faulty data-center resource available to receive the application component; generating, if the service-healing task is generated a rolling-upgrade task instructing that the application component is to be transferred to the non-faulty data-center resource; and executing, if the service-healing task is generated a rolling-upgrade background monitor that processes the rolling-upgrade task and that reallocates the application component to the non-faulty data-center resource.