Mongoose: Schema vs Model?

Question

When looking at tutorials there is often a delineation between a schema and a model, particularly when dealing with mongoose/mongodb. This makes porting over to postgresql somewhat confusing, as 'models' don't seem to exist under that system. What is the difference the two approaches?

For example, what would be a postgres/sql ORM equivalent of this line?

(mongoose and express.js):

var userSchema = schema.define('local', {
    username:       String,
    password:       String,
});

module.exports = mongoose.model('User', userSchema);

Solution 1

In mongoose, a schema represents the structure of a particular document, either completely or just a portion of the document. It's a way to express expected properties and values as well as constraints and indexes. A model defines a programming interface for interacting with the database (read, insert, update, etc). So a schema answers "what will the data in this collection look like?" and a model provides functionality like "Are there any records matching this query?" or "Add a new document to the collection".

In straight RDBMS, the schema is implemented by DDL statements (create table, alter table, etc), whereas there's no direct concept of a model, just SQL statements that can do highly flexible queries (select statements) as well as basic insert, update, delete operations.

Another way to think of it is the nature of SQL allows you to define a "model" for each query by selecting only particular fields as well as joining records from related tables together.

In other ORM systems like Ruby on Rails, the schema is defined via ActiveRecord mechanisms and the model is the extra methods your Model subclass adds that define additional business logic.

Solution 2

A schema is fundamentally describing the data construct of a document (in MongoDB collection). This schema defines the name of each item of data, and the type of data, whether it is a string, number, date, Boolean, and so on.

A model is a compiled version of the schema. One instance of the model will map to one document in the database. It is the model that handles the reading, creating, updating, and deleting of documents. A document in a Mongoose collection is a single instance of a model. So it makes sense that if we're going to work with our data then it will be through the model. A single instance of a model (like a User instance in var User = mongoose.model('User', userSchema);) maps directly to a single document in the database. With this 1:1 relationship, it is the model that handles all document interaction - creating, reading, saving, and deleting. This makes the model a very powerful tool.

Taken from "Mongoose for Application Development", by Simon Holmes, 2013

I imagine models as classes created from a schema (maybe I am mistaken).

MongoDB stores everything in BSON , which is a binary format. A simple Hello World BSON document might look like this internally: \x16\x00\x00\x00\x02hello\x00\x06\x00\x00\x00world\x00\x00. A computer can deal with all that mumbo-jumbo, but that's hard to read for humans. We want something we can easily understand, which is why developers have created the concept of a database model. A model is a representation of a database record as a nice object in your programming language of choice. In this case, our models will be JavaScript objects. Models can serve as simple objects that store database values, but they often have things like data validation, extra methods, and more. As you’ll see, Mongoose has a lot of those features.

Taken from "Express in Action", by Evan Hahn, 2016

Comments

[dnv]

Thanks for the answer. I see in some places a User object is still created like this and called a 'model' even using postgres: "var User = sequelize.define('user', { field:value});" which is passed into the main app. Is this simply a schema definition? Source is sarabinns.com/tag/passport-js-sequelize-postgresql

[Peter Lyons]

The {field:value) part is the schema. The User part is the model.