PM2 VS node-windows

There are plenty of ways to accomplish this: Docker, Kubernetes, Pulumis, etc., but I don’t like to add too much complexity. So for a basic app, I like to use PM2, a Node.js process manager with great features, including the ability to run our app in the background.

This project will consist of a single "index.js" file that you can deploy anywhere. I recommend using an Nginx reverse proxy and pm2 to keep the service running.

Your app should be running now. To be able to run the app in the background, I will use pm2. Stop your application using "Ctrl + C" and install pm2

https://www.npmjs.com/package/pm2 I found this package. It looks good and solves my problem, I think.

Usually, you have something that restarts it for you. This is what a "process manager" is for, e.g. https://www.npmjs.com/package/pm2 But in most more advanced systems, this is taken care of for you differently. E.g. lambdas are restarted automatically based on how many instances are needed. If you are in container-land, there's usually a health check endpoint on your server that gets pinged by the container orchestrator, and if there's no response, it will kill and redeploy the container.

Additionally, it provides many more features to manage and visualize the processes. More details on PM2 can be found in their official documentation.

We will use the official nodejs library for interacting with the service bus and the node-windows package to create the Windows service.