Awesome javascript library for building real time, fast, scalable applications
August 31, 2021

Awesome javascript library for building real time, fast, scalable applications

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Node.js

Node.js is used for developing the backend of my current organization's ongoing product. Node.js is not used by the complete organization but only the backend developer team. Our current product needed a multi-tenancy (concurrency) feature which is developed using Node.js only. Also, our product's frontend was written in javascript so to match the language Node.js was used and other problems like fast performance of product, scalability, non-blocking event-driven architecture, etc. were solved.
  • Node.js provides a feature called callback and promise. This feature lets the code get executed faster and hence increases the performance of the application.
  • Node.js makes the application scalable. The application becomes scalable due to load balancing. We can have multiple jobs for a node to process and it can handle it giving high throughput with no significant burden.
  • We needed a feature called multi-tenancy in our product's enterprise which was very effectively provided by Node.js.
  • Also, Node.js provides real-time data-intensive applications which were a must for our e-learning product.
  • The biggest drawback of Node.js even now is its inability to process CPU-bound tasks. For computation-intensive applications, PHP is preferred over Node.js. Whenever a heavy request comes to the event loop, Node.js would set all the CPU available to process it first, and then answer other requests queued. That results in slow processing and overall delay in the event loop, which is why Node.js is not recommended for heavy computation. Node.js should work upon this feature too.
  • Due to its asynchronous nature, Node.js relies heavily on callbacks, the functions that run after each task in the queue is finished. Keeping a number of queued tasks in the background, each with its callback, might result in the so-called callback hell, which directly impacts the quality of code. This should also be improved.
  • There are some modules in the npm registry which are not of good quality so these should be worked upon.
  • It's event driven architecture and fast processing feature.
  • Light weight model architecture
  • it provides Scalable technology for microservices
  • Robust technology stack
  • Our product has become very efficient in terms of optimization, scalability as well as performance
  • the application is not performing much efficiently when a feature involves lot of computations
  • Also, our product was able to solve the problem of real-time data displaying effectively using node.js
Node.js provides features that were used to solve the problem and overall there was no negative impact. That is why Node.js is selected.

Do you think Node.js delivers good value for the price?

Yes

Are you happy with Node.js's feature set?

Yes

Did Node.js live up to sales and marketing promises?

Yes

Did implementation of Node.js go as expected?

Yes

Would you buy Node.js again?

Yes

1. Node.js is useful for building one page, fast, light-weight, scalable applications.
2. It is not suitable for building computationally extensive applications, it may lead to bad performance.