openfaas-templates VS Mongoose

A custom NodeJS OpenFaaS template that uses MongoDB and Mongoose to manage the data models

To set up the project, create an empty folder and initialize a node project within that folder by runningnpm init on the command line. Then, install relevant packages. Mongoose will serve as our node library to interact with our Mongo DB server. Thereafter, proceed to set up the project and ensure the MongoDB is connected to the Node JS application.

We prefer randomly generated access tokens that we store in MongoDB using an AccessToken Mongoose model over JWTs. JWTs are faster, because you don't need a database round trip to validate a JWT.

If your application doesn't necessitate raw SQL/NoSQL, opt for Object-Relational Mappers (ORMs) like Sequelize or Object-Document Mappers (ODMs) like Mongoose for database queries. They feature built-in protection against injection attacks, such as parameterized queries, automatic escaping, and schema validation, and adhere to some security best practices.

Mongoose

Mongoose: MongoDB object modeling in the application to manage mongodb queries and collections in a easier and hassle free way.

In this article, we explored how to use bcrypt in a Node.js application with Mongoose to securely hash and verify passwords. We covered the installation of bcrypt, the implementation of password hashing using Mongoose pre save middleware, and the use of Mongoose instance methods for password comparison during login. By following these steps, you can enhance the security of your application authentication system, ensuring that user passwords are properly protected.

Mongoose: ORM, for connecting to MongoDB.

To manage user auth we need to create a user account - identification. So, let's install mongoose and jsonwebtoken to handle JWT authentication - an alternative to creating a user session when a user logs in

If your application uses MongoDB's Node.js driver or Mongoose ODM, occasionally you may observe errors such as querySrv ECONNREFUSED _mongodb._tcp.cluster0.abcde.mongodb.net or Error: querySrv ETIMEOUT _mongodb._tcp.cluster0.abcde.mongodb.net being thrown. The MongoDB Atlas documentation outlines several methods to troubleshoot connection issues, including how to handle "Connection Refused using SRV Connection String" scenarios, but why does this happen in the first place?