Alternatives to PM2 logo

Alternatives to PM2

Docker, forever, nodemon, NGINX, and Supervisord are the most popular alternatives and competitors to PM2.
464
321
+ 1
23

What is PM2 and what are its top alternatives?

Production process manager for Node.js apps with a built-in load balancer
PM2 is a tool in the Node.js Process Manager category of a tech stack.
PM2 is an open source tool with 37.8K GitHub stars and 2.5K GitHub forks. Here’s a link to PM2's open source repository on GitHub

Top Alternatives to PM2

  • Docker
    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • forever
    forever

    It is a simple CLI tool for ensuring that a given script runs continuously. It is used to keep the server alive even when the server crash/stops. When the server is stopped because of some error, exception, etc.it automatically restarts it. ...

  • nodemon
    nodemon

    It is an open source utility that will monitor for any changes in your source and automatically restart your server. It has a default support for node & coffeescript, but easy to run any executable (such as python, make, etc). ...

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Supervisord
    Supervisord

    It allows its users to monitor and control a number of processes on UNIX-like operating systems. It shares some of the same goals of programs like launchd, daemontools, and runit. it is meant to be used to control processes related to a project or a customer, and is meant to start like any other program at boot time. ...

PM2 alternatives & related posts

Docker logo

Docker

146.4K
113.9K
3.8K
Enterprise Container Platform for High-Velocity Innovation.
146.4K
113.9K
+ 1
3.8K
PROS OF DOCKER
  • 823
    Rapid integration and build up
  • 689
    Isolation
  • 519
    Open source
  • 505
    Testa­bil­i­ty and re­pro­ducibil­i­ty
  • 459
    Lightweight
  • 217
    Standardization
  • 184
    Scalable
  • 105
    Upgrading / down­grad­ing / ap­pli­ca­tion versions
  • 87
    Security
  • 84
    Private paas environments
  • 33
    Portability
  • 25
    Limit resource usage
  • 16
    Game changer
  • 15
    I love the way docker has changed virtualization
  • 13
    Fast
  • 11
    Concurrency
  • 7
    Docker's Compose tools
  • 5
    Fast and Portable
  • 5
    Easy setup
  • 4
    Because its fun
  • 3
    Makes shipping to production very simple
  • 2
    It's dope
  • 2
    Highly useful
  • 1
    Very easy to setup integrate and build
  • 1
    Package the environment with the application
  • 1
    Does a nice job hogging memory
  • 1
    Open source and highly configurable
  • 1
    Simplicity, isolation, resource effective
  • 1
    MacOS support FAKE
  • 1
    Its cool
  • 1
    Docker hub for the FTW
  • 1
    HIgh Throughput
CONS OF DOCKER
  • 8
    New versions == broken features
  • 6
    Unreliable networking
  • 6
    Documentation not always in sync
  • 4
    Moves quickly
  • 3
    Not Secure

related Docker posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.8M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 5.4M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
forever logo

forever

68
104
0
A simple CLI tool
68
104
+ 1
0
PROS OF FOREVER
    Be the first to leave a pro
    CONS OF FOREVER
      Be the first to leave a con

      related forever posts

      nodemon logo

      nodemon

      1.5K
      156
      2
      A simple monitor script for use during development of a node.js app
      1.5K
      156
      + 1
      2
      PROS OF NODEMON
      • 1
        Easy to use
      • 1
        It's lightweight
      CONS OF NODEMON
        Be the first to leave a con

        related nodemon posts

        NGINX logo

        NGINX

        103.4K
        52.2K
        5.5K
        A high performance free open source web server powering busiest sites on the Internet.
        103.4K
        52.2K
        + 1
        5.5K
        PROS OF NGINX
        • 1.4K
          High-performance http server
        • 893
          Performance
        • 728
          Easy to configure
        • 606
          Open source
        • 529
          Load balancer
        • 287
          Free
        • 287
          Scalability
        • 223
          Web server
        • 174
          Simplicity
        • 135
          Easy setup
        • 29
          Content caching
        • 20
          Web Accelerator
        • 14
          Capability
        • 13
          Fast
        • 11
          High-latency
        • 11
          Predictability
        • 7
          Reverse Proxy
        • 6
          Supports http/2
        • 5
          The best of them
        • 4
          Great Community
        • 4
          Lots of Modules
        • 4
          Enterprise version
        • 3
          High perfomance proxy server
        • 3
          Embedded Lua scripting
        • 3
          Reversy Proxy
        • 3
          Streaming media delivery
        • 3
          Streaming media
        • 2
          Fast and easy to set up
        • 2
          Slim
        • 2
          Blash
        • 2
          Lightweight
        • 2
          saltstack
        • 1
          Virtual hosting
        • 1
          Along with Redis Cache its the Most superior
        • 1
          Ingress controller
        • 1
          Narrow focus. Easy to configure. Fast
        • 1
          GRPC-Web
        CONS OF NGINX
        • 8
          Advanced features require subscription

        related NGINX posts

        Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

        We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

        See more
        Gabriel Pa
        Shared insights
        on
        TraefikTraefikNGINXNGINX
        at

        We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

        We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

        The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

        See more
        Supervisord logo

        Supervisord

        112
        88
        0
        A client/server system that allows its users to monitor and control a number of processes
        112
        88
        + 1
        0
        PROS OF SUPERVISORD
          Be the first to leave a pro
          CONS OF SUPERVISORD
            Be the first to leave a con

            related Supervisord posts