title: Is nodejs representing Reactor or Proactor design pattern?
body: <p>Many articles online demonstrates nodejs as an example of reactor pattern. Isn't it rather proactor?</p>
  
  <p>As far as I understand, the difference between the two is:</p>
  
  <ol>
  <li><a href="https://en.wikipedia.org/wiki/Reactor_pattern" rel="nofollow noreferrer">reactor handles events in a single thread (synchronously)</a>,</li>
  <li><a href="https://en.wikipedia.org/wiki/Proactor_pattern" rel="nofollow noreferrer">proactor handles events is multiple threads (asynchronously) with completion callbacks</a>.</li>
  </ol>
  
  <p>For example in <a href="https://hackernoon.com/the-node-js-system-51090c35dddc" rel="nofollow noreferrer">this article</a>:</p>
  
  <blockquote>
    <p>Reactor Pattern is an idea of non-blocking I/O operations in Node.js. This pattern provides a handler(in case of Node.js, a callback function) that is associated with each I/O operation. When an I/O request is generated, it is submitted to a demultiplexer.</p>
  </blockquote>
  
  <p>Isn't it actually definition of proactor?</p>