API Guide | restify: "Why use restify and not express?
I get asked this more than anything else, so I'll just get it out of the way up front.
Express' use case is targeted at browser applications, and contains a lot of functionality (i.e., templating/rendering) to support that. Restify does not. Restify exists to let you build "strict" API services that are maintanable and observable; restify comes with automatic DTrace support for all your handlers, if you're running on a platform that supports DTrace.
In short, I wrote restify as I needed a framework that gave me absolute control over interactions with HTTP and full observability into the latency and characteristics of my applications. If you don't need that, or don't care about those aspect(s), then it's probably not for you."
'via Blog this'
