Proper organization of connection to the database in NodeJS?

Question

Node.js

I still have an unfinished Telegramm bot on NodeJS. Here I try to do everything more or less competently. A question arose despite the fact that I realized that apparently I didn’t do the logic of connecting to the database correctly.

I have a db.js file - in it in the constructor there is a connection to the database. But I connect and create a database object in each controller (which is created for each schema model (bd)) - a kind of MVC.
As you understand, there will be many connections with this approach.
Then it may be easier to write to the session (Telegraf) what will be available on all scenes for the client. Or can eat what other ways on easier - easier?

Answer 1

Yes, you can use Sequelize and forget about manual management of the database and queries, or throw the database object into those modules that use it.

Answer 2

Try to make a DB class, which will describe all the methods of working with the database (connection, disconnection, addition, update, etc.), and then create an object that you will import into all controllers.
Connect and disconnect the base in each method.
For example, there will be a call like: which does: 1. Connect to the server 2. Add an argument to the database 3. Disconnect from the server
database.add("test")