NodeJS for project development?

Question

Node.js

I am interested in development on NodeJS, I want to try to write a project on it. I recently came across a post that was written over a year ago, in which NodeJS is presented as a "Cancer" and makes fairly objective arguments. I wanted to find out from the community the attitude to NodeJS today. Surely a lot of changes have taken place during this time and it has become much better for use in production.
Share your experience of developing highload projects on NodeJS and tell us what type of services it is most suitable for.

Answer 1

For the second year now, my client has been using the system of informatization of production processes in window production (eurowindows). Tasks of the system:
- demonstration of technological maps of products on the conveyor sections;
— fixing operations with products;
– providing real-time data on the state of individual products and the overall state of production;
— analytics of production at sites and specific employees;
— accounting for quality control;
— warehouse accounting of finished products and double-glazed windows;
— planning the schedule of shipment from the warehouse;
- automatic notification of customers about the readiness of the order by SMS;
All system interfaces are implemented as real-time web applications using Socket.io.
The system was written in NodeJS version 0.6, then it was transferred to 0.8 and now to 0.10. There were no problems with the transition.
The maximum uptime of the NodeJS system process that we managed to observe is 112 days. No memory leaks have been recorded during this time.
For me, after developing such a solution, the question of the seriousness of NodeJS is no longer an issue. He himself was a staunch perlist. Now there is no desire to write on anything other than NodeJS.

Answer 2

Maybe there is not much in the Java script, but it works very quickly, I have only one project on it, but I still don’t understand how it works and quickly calculates all users online, I always thought before that javascript was slow.

Answer 3

node.js in its current implementation in conjunction with npm (not to write everything from scratch, but to assemble it as a constructor from already written modules) is an excellent solution for a project of any scale, including, for example, implementing the server part of online games (I won’t tell you which ones right now , but you can search). One of its important advantages is one language for client-side and server-side, as well as native and simple asynchrony in conjunction with the same socket.io especially.

Answer 4

Javascript lacks strong typing, normal classes, and other joys of serious languages. As I understand it, this makes it unsuitable for any somewhat large and complex applications (Java level and dotnet applications). True, I have experience only with browser-based javascript, and not with a node.

Answer 5

Most suitable for projects with a lot of I / O operations with low CPU consumption, real-time applications, data streaming. I have not been lucky enough to do a serious highload on Node.js yet, but on medium loads it behaves with dignity and without problems.
Recently I ran a small piece of code with arithmetic in a loop and on a large number of iterations V8 turned out to be 70-90 times faster than PHP.

Answer 6

Node.js is a very flexible development tool. At the moment, a huge number of high-quality modules have already been written that can simplify development. And if for some reason you don’t like javascript, then you can always develop in CoffeeScript and get a more convenient syntax for creating classes, meta-programming opportunities and other goodies :)

Answer 7

The post-translation you link to was a clear troll, the original was deleted long ago. There, a person wrote a blocking function and blames node.js for not being able to magically make it non-blocking. Here is a good article .

Answer 8

I recently also took a look at node.js and I will write this: now this thing is not included in ANY package manager from the Linux world, even in Fedora they plan to include it only in the next version. From this I concluded that for production it is suitable only for the most ardent fans who do not care about everything and in case of problems they will finish it themselves.
But the thing itself is interesting. There aren't many backends in programming languages ​​that aren't purely OOP based.

Answer 9

We use node.js in our startup Skwibl .
Of the benefits:
+ Holds loads well (so far the loads on the project are not large, but under tests locally kept about 4500 connections)
+ Fast development (in conjunction with coffee-script, the description of the problem becomes very concise)
+ Saves the resource of the team (one language for the server and client, so you don’t need to assemble a large team)
+ Flexibility (all the advantages of a dynamic language on the server)
+ Responsive community (in mailing lists they answer questions quite quickly, they try to help)
Of the minuses:
- Immature libraries (quite a lot of modules still suffer from childhood diseases often have to write patches)
- Lack of standards (at first I had to cycle a lot to write the site architecture)
In general, it’s very pleasant to write and I don’t want to return to Java. Libraries will gradually grow up and there will be fewer problems.

Answer 10

Read the Habrahabr hub about Node , there are answers to your questions.