I have an intuition that Node.js can fruitfully front-handle user web requests, then pass them to Ruby/Rails, when doing this:
* In the case that processing requests (from users) requires collecting information from elsewhere, like various web service APIs (very common, now!).
Node.js would handle the (long) event queue thus generated, then send HTTP requests to Ruby/Rails, forging the sender in the header like the users'.
Then, Ruby/Rails won't block for very long, only long enough for the database.
Node.js could put the info anywhere, like the URL or in a fast database.
Copyright (c) 2011 Mark D. Blackwell.