Node.js Reviews and Ratings

Use Cases and Deployment Scope

Node.js is commonly spread across the organization as a service aggregator of other services, acting as a Backend For Frontend for the web and native applications.

Since the frontend technologies are JavaScript-based, it's easy to use, having high-speed development from all developers, because all of them are familiarized with the base language.

Likelihood to Recommend

Node.js is a strong choice for building modern applications. It simplifies managing how different services work together (service orchestration) and adapts to growing user demands (scalability). Additionally, it allows for efficient Backend for Frontend (BFF) layers, providing web applications with the specific data they need. Also, Node.js utilizes JavaScript, a familiar language for many developers, which can streamline the development process.

Use Cases and Deployment Scope

We use Node.js to develop a single-page app like chat applications, chat boat, etc as a backend, which is widely using in our organization with this we are managing both frontends as well as backend with the help of javascript.it really provides a smooth user experience for users for multiple requests without any delay.

Likelihood to Recommend

Suited For:

<ul><li>A single-page application that provides a quick response.</li><li>Easy to maintain for a single-page application.</li></ul>Not Suited for:

<ul><li>The complex application that produces callback hell.</li></ul>

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

Node.js is my absolute favorite tech stack to work with, I learnt it at a time when I was burnt out and bored with .NET after having been in the Microsoft world for most of my career. Even with .NET Core around, I still prefer Node.js to anything else. Node is robust and fast, it delivers on everything it promises, it is the back bone of many services at my organization and used across all departments. When you get something like Node.js for free and it is such a pleasure to work with, all you can say is that it's contribution to the organization is priceless.

Likelihood to Recommend

If you need a fast, robust and reliable server side framework that allows you to write JS on the backend and therefore have your project in one language - Node.js is a stand out choice. It can easily handle heavy traffic on very little resources (CPU and memory usage is very efficient). I can't recommend it enough, it is such a pleasure to work with - I feel it gave me back my career. I was so bored with the banality of .NET, I had also come to dislike it's overly convoluted and complicated class structure. Node.js was the fresh start I needed, it can be as simple or as complicated as you like - but even at it's most complicated it can still beat the pants off .NET core any day.

Use Cases and Deployment Scope

Node.js is used by me and my department for making backend of many web projects. We use it ideally for making backend of projects in which we have to serve data dynamically to webpages. We also use it mostly for designing backend API and for making web applications with backend and frontend in the same directory.

Likelihood to Recommend

Node.js is well suited when we have to serve data to display on a webpage, which will be loaded once the page is load and doesn't make too many requests, or for a small application with fewer visits as for big projects we couldn't rely on a single environment or language.

Use Cases and Deployment Scope

In our organization Node is used for backend application development. We have several applications that manage communication between end users and Facebook Messenger. We use weebhooks and express.js package to manage this. As alternative we could use Python but Node was better choice for us. Mainly because of its simplicity and many additional packages with ready to use addons. Moreover we have few JS dev on board so it was easier to develop apps.

Likelihood to Recommend

The ability to process multiple concurrent requests by Node.js is desired for Internet of Things projects that may have thousends or even more devices connecting at the same time.

Use Cases and Deployment Scope

We are using Node to implement a microservices architecture that runs every aspect of the product. From a user-facing API, to back-end processing services, to our serverless triggers.

Likelihood to Recommend

Node is very good at microservices. "Do one thing and do it well." It is easily Dockerized and scalable. For many products, Node can be used as a front-end API, as well as a back-end processor.

For extremely CPU-intensive tasks, like advanced machine learning, I'd recommend not to use Node.