title: Process manager with Python
body: <p>The system I have in mind looks like a client-server app, with a simple REST API, where the clients can ask the server to start "worker processes" for a given task (POST), query their existence (GET) and stop them (DELETE).</p>
  
  <p>The "worker process" (I don't know how to call it - that's why the question's title is so bad) runs in the background, in my case, this is a connection to an industrial control system, where a Python functions acts as a callback triggered by external events. Basically this is data acquisition.</p>
  
  <p>So the <code>client</code> asks the server to start a process to do the data acquisition of something, until it asks the server to stop it.</p>
  
  <p>Does that translates to a common problem that has a nice solution?</p>
  
  <p>The question is not about the REST part, but on the part where the server manage services.</p>
  
  <p>It does <strong>not</strong> seem to be solved using a asyn queue and a pool of workers...</p>