I have never used mongojs, but it seems to be similar to mongodb, which is a simple encapsulation of the MongoDB API.
My suggestion is that if it is an application, that is, a user-oriented project, such as a website, then use mongoose. mongoose is currently the best MongoDB ORM in Node.js. By pre-defining Schema, mongoose can help you complete part of the data verification and process control work, speeding up development.
If it is a library that may be referenced by other projects, I recommend using MongoDB’s native API directly, because in this case, the documents in the collection often do not have a specific pattern and cannot take advantage of the functions of mongoose. At the same time, there is usually less repetitive logic in the library than in the application, and using a simple API will provide greater flexibility.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
I have never used mongojs, but it seems to be similar to mongodb, which is a simple encapsulation of the MongoDB API.
My suggestion is that if it is an application, that is, a user-oriented project, such as a website, then use mongoose. mongoose is currently the best MongoDB ORM in Node.js. By pre-defining Schema, mongoose can help you complete part of the data verification and process control work, speeding up development.
If it is a library that may be referenced by other projects, I recommend using MongoDB’s native API directly, because in this case, the documents in the collection often do not have a specific pattern and cannot take advantage of the functions of mongoose. At the same time, there is usually less repetitive logic in the library than in the application, and using a simple API will provide greater flexibility.
Just search on google, there are comparisons and answers to your questions on stackoverflow