A design pattern for a module that constantly checks if other modules are working in the system?

Question

I am implementing a java project where there are several decoupled modules interacting with a common service (database / web service).

There is a health check module that continuously checks all modules to make sure that they work or not. If it is detected that the module is inactive or does not work properly, the health check module repairs and restarts it.

What behavioral pattern will belong?

Answer 1

, .

, , , . , , .

, Singleton.

MSDN , , .

this.

Answer 2

. , , .

Healthchecker . .