Currently, server.js sort of just expects to run... forever, which has some bad implications. For example, connections to MongoDB will never be disposed of, which isn't bad on the surface, but may have a negative impact on MongoDB if it has a limited connection pool.
We should implement some sort of graceful shutdown process for the server that properly disposes of things like connections.
Currently, server.js sort of just expects to run... forever, which has some bad implications. For example, connections to MongoDB will never be disposed of, which isn't bad on the surface, but may have a negative impact on MongoDB if it has a limited connection pool.
We should implement some sort of graceful shutdown process for the server that properly disposes of things like connections.