My Thoughts and Conclusions About Two Different Ways of Doing Something Concerning Server's Approaches Using Node.js vs. Apache Comparison Example
When the major problem is the number of persons to travel, matter less if the car has front-wheel drive or rear-wheel drive.
Number of seats care most.
Being straight, more requests demand more resources and increase possible concurrencies issues.
It matters less how the process requests are handled, but how the project's resources in general may scale with high availability.
Putting aside that, if you have light CPU processing per request, Node.js will be lighter approach, otherwise, if it is not possible to guarantee that, threads will fit better, so Apache is a better choice.
See more at:
http://www.quora.com/What-are-the-pros-and-cons-of-Node-js-versus-Apache-web-server
http://voidcanvas.com/describing-node-js/
http://www.toptal.com/nodejs/why-the-hell-would-i-use-node-js
https://thomashunter.name/blog/php-vs-nodejs/
No comments:
Post a Comment