The competition in the server side programming department is getting tougher with each month, especially with the recent popularity of NodeJS. However let`s look how everything began.
PHP appeared about 20 years ago, in 1995 and ever since then it has been a number one language for back-end developers and has gathered a big community behind it. For a long time there wasn’t any good reason why not to use PHP: its rather easy to use PHP, it
s supported by the majority of hosting companies and it has become the most commonly used language in terms of number of websites powered by it.
NodeJS was created in 2009 and it was very unique to all the other back end languages. It`s an efficient and scalable software platform that can execute JavaScript code on a server. NodeJS uses event-loops rather than traditional threading, which makes it faster and less memory-intensive than traditional platforms. Thus the ability to use Javascript on both the client and the server and the ability of NodeJS to run asynchronously have undoubtedly lead to the rise of NodeJS and its popularity within developers and customers.
Of course, everyone has his own truth: one coder will praise the speed of NodeJS while the other will be devoted to the stability and long history of PHP. But let`s have a look at strong sides of both for you to decide whether to concern yourself with the so popular nowadays NodeJS or not.
PHP strong sides:
- Huge community and tons of materials for all programmers, from a beginner to an advanced coder.
- Deep code base. The most popular platforms for building websites (WordPress, Drupal, Joomla) are written in PHP. Not only are the platforms open source, but so are most of their plug-ins.
- Easy to find a hosting company. PHP has been the industry standard since the stone age and any hosting company still surviving is bound to be compatible with it. For Node.JS you still need to make a little research.
- Simplicity. PHP can be run inside of the same file as html.
- Speed of coding. For most developers, writing PHP for Web apps feels faster: no compilers, no deployment, no JAR files or preprocessors — just your favorite editor and some PHP files in a directory.
- Mixing code with content. You just open up PHP tags and start writing code. No need for templates, no need for extra files or elaborate architectures.
- No client app is needed. All of the talk about using the same language in the browser and on the server is nice, but what if you don’t need to use any language on the browser? PHP is a way out.
NodeJS strong sides:
- Speed. NodeJS is blazing fast compared to PHP. This is where Node really kicks assJ.
- Separation of Concerns. NodeJS separates fundamental components up giving a clear separation of concern across controllers / routes, models and views.
- New and fresh. It’s newer in comparison to PHP and has been developed by programmers who have full knowledge and understanding of modern web applications, from the server to the client, and that means more modern features.
- Modern syntax. Javascript isn’t perfect and it may drive developers crazy, but overall it’s a modern language that supports modern syntax such as closures, and you can easily extend Javascript and make any object configured to exactly how you need it.
- JSON. NodeJS is a powerhouse for JSON. Accessing SQL is possible and there’s plenty of plugins that make it possible, but JSON is the lingua franca for interacting with many of the latest NoSQL databases.
- Gridlock. NodeJS uses a callback structure to pass logic from one asynchronous call to the next meaning we never have to worry about spawning new threads or even considering the deadlock process. Almost no function in Node directly performs I/O, so the process never block which is a major implication for scalable systems.
That is a difficult decision when it comes up to decide which language or tool to choose. But NodeJS worth considering and it`s proved by the fact that Node is getting more and more popularity every day. And what is your opinion on NodeJS, is it the future of web?

Anna Kozik
Business Development Manager
You forgot one of the bigger points: with node you get a language that works on the client and server; with PHP you will still need Javascript anyway, for the client. This means that you can actually write code that works both on the client and server or move functionality from one focus to the other, and you can hire devs that have full stack expertise a lot easier.
Regarding separation of concerns: That’s up to the developer. Welcome to MV* programming, it’s not unique to nodejs. Anyone can do it.
Regarding modern syntax: Regardless of any fanboys or haters of either language, you can do nearly anything you want in either language.
Regarding JSON: PHP has flexible objects/arrays just like javascript and works with JSON and objects just as easily. I don’t see the amazement over nodejs on this point.
The only thing NodeJS shines on, is speed and the lack of grid lock — provided we have the hardware resources for everything. Everything else is fluff whether it’s PHP or javascript — it doesn’t really matter.
I really am not bashing on node, even if it seems like it. I’m just saying that these things aren’t unique to node.
Hi
I don’t consider to use PHP as is and not at all mixing content and code. It’s a mess.
But I love PHP.
I consider PHP only with Symfony 2 framework which include MVC logic like NodeJs.
So why switching to nodeJS ?
I don’t use NodeJs so here are the arguments I imagine (the same than yours) : same language than front end, easy to manipulate JSON and DOM trees (complicated on PHP).
By the way, you are red pretty 😉