Why do we need, what advantages to use mongoose [c

问题:

I have just started up with mongodb and I recently gone through Mongoose, an ODM framework.

On the documentation, I couldn't find why we need to use Mongoose. One reason I can give is we can define application schema from Mongoose.

I am looking for more possible reasons, and needs that will attract me to use Mongoose.

Please list all possible advantages and reasons/needs why use Mongoose.

回答1:

Main advantage is abstraction over pure mongo.

Many developers who come from SQL database types feel very uncomfortable working with dynamic collections that have no structure defined. So Schemas in the first place helps with that.
Additionally, it implements validation and other neat features in order to make sure your schema is consistent when inserting/updating/finding documents from collections.

It also creates Model abstraction which makes it easier to work with, so it looks like you are working with just objects rather than pure data.

There are many other goodies like middleware, plugins, population, validation. Please check mongoose docs for more information:

Personally, I prefer pure mongo as it is more consistent with official 10gen mongo docs and does not create abstractions that always costs some limits and rules that you will have to follow.

回答2:

If you are working with Node.js and you are pretty new NoSQL I'd recommend using the the native Node Driver(mongodb) at first.

Reasons:

1. The syntax between the Node Driver and the Mongo shell is very similar and so you'll get a quicker grasp of how to use MongoDB in general.

2. Models are only useful when you are scaling into a big application with a large API that needs to be broken up into a MVC system(mongoose being your models).

Pros/Cons of using Mongoose:

Pros:

• Biggest Pro is that it has the data validation built into it(requirements of what data you will allow to be added or to update your database). It will take some work to build that yourself.(but not THAT hard)
• It will abstract away most of the mongoDB code from the rest of the application.

Cons

• Biggest con is starting off with schemas right out of the gate will really defeat the purpose of using NoSQL and it will be hard to experience what is good about having a loose structured data system during the stages of rapid development.

• Not all of your data operations will nicely fit into a characterization that can be encapsulated with a model. Encapsulation is especially hard initially - unless you have a very clear idea of the data flow before you start (which is ideal, but not easy when you are building something conceptually new and requires a lot of experimentation and change/redesign).