Elastic Beanstalk Node.Js needs PM2 or Forever

Question

In my local node server , it fails on any uncaught exception and has to be manually restarted. So local was run using either forever or pm2. But my development server is AWS Elastic Beanstalk with Node.Js environment .Though it logs uncaught exceptions and throws it , it never terminates.Even if it terminates , it starts automatically. So is there a need for PM2 or Forever to keep node.js running for ever in AWS Elastic Beanstalk environment.

Accepted Answer

My 2 cents:

There are many advantages for PM2 over EBS:

with PM2 you can control and manage many applications (processes) with different platforms (JS, Ruby, ...). Where in EBS you can deploy only one application at a time to an EBS.

PM2 gives you direct control over all running process, where you can reload/restart/stop one process and keep other intact.

EBS can fix only few problems for you, like restart on crash, or limit memory leaks. But PM2 gives you control over many other problems (graceful reload, 0 latency reload, ...) Now, I might be a little bit wrong about the full functionalities of EBS, and it might be providing more

Elastic Beanstalk Node.Js needs PM2 or Forever

Solution

Problem