title: Using worker/background processes in node.js vs async call
body: <p>I want to know if there is any benefit in passing off db or other async calls to a worker process or processes. Specifically I'm using heroku and postgres. I've read up a good bit on node.js and how to structure your server so that the event loop isn't blocked and that smart architecture doesn't leave incoming requests hanging longer than 300ms or so.</p>
  
  <p>Say I have the following:</p>
  
  <pre><code> app.get('/getsomeresults/:query', function(request, response){
      var foo = request.params.query;
      pg.connect(process.env.DATABASE_URL, function(err, client, done) {
              client.query("SELECT * FROM users WHERE cat=$1", [foo], 
              function(err, result){
              //do some stuff with result.rows that may take 1000ms
              response.json({some:data})
              });
      });
   });
  </code></pre>
  
  <p>Being that postgresql is async by nature is there any real benefit to creating a worker process to handle the processing of the results set from the initial db call?</p>