title: Node.js child processes on Heroku with single Dyno
body: <p>Pardon my ignorance, I'm currently learning how to use Node coming from a PHP background where I really had no interaction with Apache or server management. I'm using Heroku to host my Node projects, pushed straight from the Cloud9 IDE.</p>
  
  <p>From what I've read, a Heroku dyno is a single web process, buying additional dynos will allow you to deal with more traffic coming in because by increasing dynos you increase the size of the amount of requests that you can deal with at any one time.</p>
  
  <p>I know the Node is a single-threaded system that deals with requests one by one, allowing you to spawn child processes for anything that may take some time to deal with (like database requests, processing files etc). </p>
  
  <p>So what happens in Heroku if I spawn a child process with a single dyno? Does this not need another dyno to work on? Surely if Node is running a single process and I only have one process available in my single dyno any extra processes are going to have to be handled by that one too?</p>
  
  <p>Or do I have this all wrong?</p>