Let's face it Nodejs is actually suitable for most of the things if we do not forget the Golden rule of not blocking the thread. When you can one should use c/c++ to boost performance. Now from Economic Perspective considering cost of hosting and other stuff sticking to php and WordPress for blogs and websites will be beneficial.

Node js is being interpreted on the fly. It makes the app too way slower (string comparisons etc.) comparing to compiled languages such as Java or GC. There is also a data model problem (garbage collector vs cpu cycles). After all, node is fun but not (and won't be) convenient for cpu intensive tasks so we should consider using some GC or JAVA components within the app.

I have been writing node apps for a few years. If your app is traditional and you want to use structured database no problem use something like Laravel. With express you need to roll everything yourself and a fullstack solution like sails.js is not mature enough (plus focuses a lot on switching the type of database you store data in, which is weird to me. So for structured, traditional web apps without real time functionality and nothing too crazy/custom Laravel or Rails or Django are better bets.

Shouldn't be built with Node.js? Nothing. Node.js is good for everything. It's by nature not performant in certain use cases or complicated to use in particular environments. By avoiding certain types of apps to be built, we can't go forward. We shall alway try to push back all kinds of borders. That applies to all languages and environments.

What wouldn't I build right now? File-based processing like video encoding. But only because I am inexperienced with certain video container formats, SIMD.js and Node.js cluster.

• Image processing
• Big data manipulation

Node.js is great at managing I/O efficiently but it is not suited for CPU-intensive tasks.

So anything that requires heavy computation use other efficient languages such as CPP or Java.

Eg. Search Engines