title: Alternative to "one thread per X" architecture?
body: <p>I have been told that I shouldn't be using "one thread per" anything aproach if I want my application to scale beyond "not so far", and that there were other architectures I should look into. Only I weren't told any of those architectures' names, and I couldn't find much on google.</p>
  
  <p>Specifically I need this for a real-time web game, mostly chat-based. I would be using web sockets, but I need to process all the incoming events (many per second per game) concurrently fast enough.</p>
  
  <p>If possible, I need this architecture to be viable in Ruby or PHP.</p>
  
  <p>Any ideas?</p>