No - a Fiber is completely different to a process/thread. The server is still evented. https://github.com/laverdet/node-fibers
Re:Ace - Sinatra for Node with Fibers
by tjholowaychuk on Wednesday February 15, 2012 @12:56PM
(#3595263)
each "fiber" still consumes a relatively large stack, so in effect you're right
So...essentially, this behaves like a traditional web server? A process listens for incoming connections, then spins up a new process/thread/fiber to handle the request?