Why should you build with Node.JS?
Time to build something with React.JS. From my experience, it is pretty good for real-time applications. So why should you build with Node.JS? The answer could be a collection of many factors like business applications and technologies possibilities of Node.JS. So let's discuss the top tech criteria of Node.js excellence:
Speed and performance
Node package manager is why your developers will deliver faster. In other words, NMP is a hub of over 800 000 pre-built libraries that can be handy by developing particular cases. By installing it with the NMP command, software engineers can develop Node js real-time app features faster by reusing ready-made code components instead of building from scratch. It uses a JSON file with the metadata of your application.
Frameworks help add new functionality to web applications faster instead of building afresh. There are a lot of popular Node.js libraries to speed up application development time. You can check the full list here.
The asynchronous and non-blocking nature of JavaScript allows the code to be speedy, which enhances the entire run-time environment. The base of Google's V8 JavaScript engine also contributes to the performance. As a result, you get end-to-end programmable on JavaScript web apps that are, by the way, interoperable, which positively influences the performance.
Microservices
In contrast to a single logical executable architecture, the microservice style fits perfectly with a Node.js lightweight nature and the event-driven I/O model. Microservice-related technologies (Docker, Kubernetes) are widely used by full-stack developers building Node.js web applications. A suite of small services, as against monolith structure, enables to address of user requests to a particular part of the application and respond from there. Such direct communication with lightweight mechanisms, typically an HTTP resource API, makes it possible to build a fast and scalable core for real-time applications.
API Integration process
Since so popular and preferred by the majority, the microservice design of application architecture led to the higher necessity of REST APIs implementation. To make the glue between those individual building blocks (microservices), developers make rules, routines, commands, and protocols. Node.js paired with Express.js outputs RESTful APIs that are a good base for enterprise software projects.
If you find this answer helpful, you may also like this article:
Microservices: turn your 10 KB index.ts into a 100 MB docker container.
A microservice is just a service that follow certain conventions. It can be deployed as a container with Docker, bare metal on a Linux or Windows machine, or any other way available to run services. Docker
Is optional.
Nice article, thanks for sharing. I agree that Node.js I good especially for IoT, audio/video processing, apps with real-time communication, etc. But it's not so good for solutions that involve CPU, for example. My colleague reviewed this technology for back-end development here https://mobidev.biz/blog/node-js-for-backend-development
I don't agree, you should build with what ever you want, its all the same for 99% of apps, what you feel comfortable with you should go with. Node is nothing special. Also, I have absolutely no idea why an indie hacker would be using micro-services, is there a real use-case for that? Usually you use it in enterprise for some use cases, or you have to scale and it is one choice of many, it's also a ton of work to build and maintain it with one developer, which usually indies are.
In short:
This comment was deleted 2 years ago.
I agree with reasons for microservice , what's your recon for starting out as Indie hacker.