I am developing a distributed system for network discovery, where the user starts a job via a master's REST API.  The master then gives the same task to several slaves (in different network segments).And the slaves send the partial results for their network segment back to the master (that processes a final result).I planned to realize both these steps with further REST APIs on both sides.  My main question is:Is there a design pattern, that tells me, how to register the slaves with the master?Further questions are:Am I using the right terminology or would you rather call the slaves agents and the master manager or whatever?Does my approach (also with the three REST APIs) make sense?  
distributed system: design pattern to register slave with master
design patterns;distributed system