Stop comparing stuff you don't understand
Note: This article was originally published at Planet PHP on 26 June 2012.PHP vs Node.js: Yet Another Versus. The summary was:
Node.js = PHP + Apache + Memcached + Gearman - overhead
What the f**k? Are you kidding me? Clearly this person has NEVER used memcached or Gearman in a production environment that had any actual load.
Back in the day, when URLs and filesystems had a 1:1 mapping, it made perfect sense to have a web server separate from theAlanguageAit is running. But, nowadays, any PHP app with attractive URLs running behind the Apache web server is going to need a .htaccess file, which tells the server a regular expression to check before serving up a file. Sound complex and awkward withAunnecessaryAoverhead? That's because it is.He believes that PHP inside Apache requires a .htaccess file. Welcome to 1999. I have not used a .htaccess file since then. Anyone that cares at all about scaling Apache would disable .htaccess files. And as for running regexs, how does he propose you decide your code path in the controller of his Node.js code? Something somewhere has to decide what code is going to answer a given request. mod_rewrite is wire speed fast and compiled in C. Javascirpt nor PHP code could ever beat that.
Node has a web server built in. Some people call this a bad thing, I call those people crazy. Having the server built in means that you don't have the awkward .htaccess config thing going on. Every request is understood to go through the same process, without having to hunt through the filesystem and figure out which script to run.
The official website is quite ugly and outdated.Really? You choose your tools based on that? I don't know what to say.
Since a PHP process starts, does some boilerplate work, performs the taks the user actually wants, and then dies, data is not persistent in memory. You can keep this data persistent using third party tools like Memcache or traditional database, but then there is the overhead of communicating with those external processes.He clearly has no understanding of how memcached is supposed to be used. You don't put things in Memcached so you can use it on the next request on this server. You put things in memcached so you can use it in any request on any server in your server pool. If you just have one web server, you can write Perl CGI scripts. Performance and up time is not important to you. If you want to share things across requests in PHP, APC and XCache fill the need very well.
The number one bottleneck with web apps is not the time it takes to calculate CPU hungry operations, but rather network I/O. If you need to respond to a client request after making a database call and sending an email, you can perform the two actions and respond when both are complete.This sums up the mythical magic of Node.js. People think just because your code is not "running" that somehow the server is not doing anything. The process does not get to go do other shit. No, that would be multi-threaded. And Node.js is not multi-threaded. It is single threaded. That means the process can only be doing one thing at a time. If you are waiting on a DB call, you are waiting. I don't care what world you think you live in. You are waiting on that DB call. How your code is structured is irrelevant to how computers actually work. The event driven nature that is Node.js is much like OOP. You are abstracting yourself from how computers really work. The further you get from that, the less you will be able to control the computer.
Node.js is a very new, unstable, untested platform. If you are going to be building a large corporate scale app with a long lifetime, Node.js is not a good solution. The Node API's are changing almost daily, and large/longterm apps will need to be rewritten often.So, if I plan on making a living, don't use Node.js. Got it. We finally agree on something.
Being so new, it doesn't have a lot of baggage leftover from days of old.AHavingAa server built in, the stack is a lot simpler, there are less points of failure, and there is more control over what you can do with HTTPAresponsesA(ever try overwriting the name of the web server using PHP?).No, why would you? It is not the web server. Apache or nginx would be your web server.
- Are you building some sort of daemon? Use Node.
- Are you making a content website? Use PHP.
Truncated by Planet PHP, read more at the original (another 1749 bytes)