mongoose vs knex vs sequelize vs bookshelf
Node.js ORM Libraries Comparison
1 Year
mongooseknexsequelizebookshelfSimilar Packages:
What's Node.js ORM Libraries?

Node.js ORM libraries provide developers with a way to interact with databases using object-oriented programming principles. They abstract the complexities of SQL queries, allowing for easier data manipulation through JavaScript objects. This leads to cleaner code and improved productivity, as developers can focus on application logic rather than database syntax. Each library has its unique features, strengths, and use cases, catering to different database systems and application requirements.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
mongoose3,481,31327,2812.57 MB19611 days agoMIT
knex2,149,45219,905874 kB1,2072 years agoMIT
sequelize2,096,65730,0622.91 MB9733 months agoMIT
bookshelf58,7726,366-2375 years agoMIT
Feature Comparison: mongoose vs knex vs sequelize vs bookshelf

Database Support

  • mongoose:

    Mongoose is specifically tailored for MongoDB, providing a rich set of features for working with document-based databases. It allows developers to define schemas and models, making it easier to manage data in a NoSQL environment.

  • knex:

    Knex is a SQL query builder that supports various SQL databases, including PostgreSQL, MySQL, SQLite, and Oracle. It provides a unified API for building queries across different database systems, making it versatile for developers who work with multiple databases.

  • sequelize:

    Sequelize supports multiple SQL dialects, including PostgreSQL, MySQL, MariaDB, SQLite, and Microsoft SQL Server. This makes it a flexible choice for developers who need to work with different relational databases in their applications.

  • bookshelf:

    Bookshelf is primarily designed for relational databases and works seamlessly with PostgreSQL, MySQL, and SQLite. It leverages Knex.js as its query builder, allowing for flexible and efficient database interactions.

Data Modeling

  • mongoose:

    Mongoose excels in data modeling with its schema-based approach, allowing developers to define the structure of documents, including data types, validation, and default values. This ensures data consistency and integrity within MongoDB collections.

  • knex:

    Knex does not provide built-in ORM features for data modeling but focuses on query building. Developers can define their own models and relationships using JavaScript objects and functions, offering flexibility but requiring more manual setup.

  • sequelize:

    Sequelize provides a powerful ORM for data modeling, allowing developers to define models, relationships, and validations. It supports various associations and provides hooks for custom logic during data operations, making it suitable for complex applications.

  • bookshelf:

    Bookshelf allows for defining models and relationships using a simple and intuitive syntax. It supports one-to-one, one-to-many, and many-to-many relationships, making it easy to represent complex data structures in a relational database.

Querying Capabilities

  • mongoose:

    Mongoose provides a rich querying API that allows developers to perform complex queries with ease. It supports query chaining, population of related documents, and various query helpers for filtering and sorting data, making it powerful for MongoDB operations.

  • knex:

    Knex provides a flexible and powerful query builder that allows developers to write raw SQL queries or use its fluent interface to construct queries programmatically. It supports transactions, joins, and subqueries, giving developers fine-grained control over database interactions.

  • sequelize:

    Sequelize offers a comprehensive querying API that supports complex queries, eager and lazy loading of associations, and built-in support for transactions. It allows developers to perform CRUD operations efficiently while maintaining a clear and organized code structure.

  • bookshelf:

    Bookshelf offers a promise-based API for querying data, allowing for easy chaining of methods to build complex queries. It supports eager and lazy loading of relationships, enabling efficient data retrieval based on application needs.

Learning Curve

  • mongoose:

    Mongoose has a steeper learning curve due to its schema-based approach and extensive feature set. Developers must understand MongoDB concepts and Mongoose-specific features to effectively utilize its capabilities, but it provides powerful tools for managing data integrity.

  • knex:

    Knex is relatively easy to learn for developers familiar with SQL, as it allows for raw SQL queries alongside a fluent API. However, it lacks ORM features, which may require additional effort for data modeling and relationships.

  • sequelize:

    Sequelize has a moderate to steep learning curve, as it offers a wide range of features and configurations. Developers need to familiarize themselves with its ORM concepts, associations, and migrations, but it provides comprehensive documentation to aid the learning process.

  • bookshelf:

    Bookshelf has a moderate learning curve, especially for developers familiar with Knex.js. Its simplicity and focus on relationships make it accessible for those new to ORM concepts, but it may require some time to master advanced features.

Extensibility

  • mongoose:

    Mongoose supports extensibility through middleware and plugins, allowing developers to add custom functionality and logic to their schemas and models. This makes it easy to enhance its capabilities without modifying the core library.

  • knex:

    Knex is highly extensible as a query builder, allowing developers to create custom functions and plugins. Its flexibility makes it suitable for various use cases, but it may require more manual work to integrate with other libraries.

  • sequelize:

    Sequelize is extensible through its hooks and plugins, allowing developers to customize its behavior and add additional features as needed. Its rich ecosystem of plugins and community support makes it a versatile choice for complex applications.

  • bookshelf:

    Bookshelf is designed to be extensible, allowing developers to create custom models and extend its functionality as needed. However, it may require additional effort to integrate with other libraries or frameworks.

How to Choose: mongoose vs knex vs sequelize vs bookshelf
  • mongoose:

    Choose Mongoose if you are working with MongoDB and need a powerful ODM that provides schema validation, middleware support, and built-in data modeling features. Mongoose is great for applications that require complex data relationships and validation rules, making it easier to enforce data integrity.

  • knex:

    Choose Knex if you want a flexible SQL query builder that allows you to write raw SQL queries while still providing a fluent interface for building queries programmatically. Knex is suitable for projects where you need fine-grained control over SQL while still benefiting from a promise-based API.

  • sequelize:

    Choose Sequelize if you are looking for a comprehensive ORM that supports multiple SQL dialects (PostgreSQL, MySQL, SQLite, etc.) and provides a rich set of features, including migrations, associations, and hooks. Sequelize is ideal for larger applications that need a robust solution for managing complex database interactions.

  • bookshelf:

    Choose Bookshelf if you need a lightweight ORM that is built on top of Knex.js, and you prefer a simple, promise-based interface for relational databases. It is ideal for applications that require a straightforward way to manage relationships and perform CRUD operations without the overhead of a full-fledged ORM.

README for mongoose

Mongoose

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Mongoose supports Node.js and Deno (alpha).

Build Status NPM version Deno version Deno popularity

npm

Documentation

The official documentation website is mongoosejs.com.

Mongoose 8.0.0 was released on October 31, 2023. You can find more details on backwards breaking changes in 8.0.0 on our docs site.

Support

Plugins

Check out the plugins search site to see hundreds of related modules from the community. Next, learn how to write your own plugin from the docs or this blog post.

Contributors

Pull requests are always welcome! Please base pull requests against the master branch and follow the contributing guide.

If your pull requests makes documentation changes, please do not modify any .html files. The .html files are compiled code, so please make your changes in docs/*.pug, lib/*.js, or test/docs/*.js.

View all 400+ contributors.

Installation

First install Node.js and MongoDB. Then:

npm install mongoose

Mongoose 6.8.0 also includes alpha support for Deno.

Importing

// Using Node.js `require()`
const mongoose = require('mongoose');

// Using ES6 imports
import mongoose from 'mongoose';

Or, using Deno's createRequire() for CommonJS support as follows.

import { createRequire } from 'https://deno.land/std@0.177.0/node/module.ts';
const require = createRequire(import.meta.url);

const mongoose = require('mongoose');

mongoose.connect('mongodb://127.0.0.1:27017/test')
  .then(() => console.log('Connected!'));

You can then run the above script using the following.

deno run --allow-net --allow-read --allow-sys --allow-env mongoose-test.js

Mongoose for Enterprise

Available as part of the Tidelift Subscription

The maintainers of mongoose and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.

Overview

Connecting to MongoDB

First, we need to define a connection. If your app uses only one database, you should use mongoose.connect. If you need to create additional connections, use mongoose.createConnection.

Both connect and createConnection take a mongodb:// URI, or the parameters host, database, port, options.

await mongoose.connect('mongodb://127.0.0.1/my_database');

Once connected, the open event is fired on the Connection instance. If you're using mongoose.connect, the Connection is mongoose.connection. Otherwise, mongoose.createConnection return value is a Connection.

Note: If the local connection fails then try using 127.0.0.1 instead of localhost. Sometimes issues may arise when the local hostname has been changed.

Important! Mongoose buffers all the commands until it's connected to the database. This means that you don't have to wait until it connects to MongoDB in order to define models, run queries, etc.

Defining a Model

Models are defined through the Schema interface.

const Schema = mongoose.Schema;
const ObjectId = Schema.ObjectId;

const BlogPost = new Schema({
  author: ObjectId,
  title: String,
  body: String,
  date: Date
});

Aside from defining the structure of your documents and the types of data you're storing, a Schema handles the definition of:

The following example shows some of these features:

const Comment = new Schema({
  name: { type: String, default: 'hahaha' },
  age: { type: Number, min: 18, index: true },
  bio: { type: String, match: /[a-z]/ },
  date: { type: Date, default: Date.now },
  buff: Buffer
});

// a setter
Comment.path('name').set(function(v) {
  return capitalize(v);
});

// middleware
Comment.pre('save', function(next) {
  notify(this.get('email'));
  next();
});

Take a look at the example in examples/schema/schema.js for an end-to-end example of a typical setup.

Accessing a Model

Once we define a model through mongoose.model('ModelName', mySchema), we can access it through the same function

const MyModel = mongoose.model('ModelName');

Or just do it all at once

const MyModel = mongoose.model('ModelName', mySchema);

The first argument is the singular name of the collection your model is for. Mongoose automatically looks for the plural version of your model name. For example, if you use

const MyModel = mongoose.model('Ticket', mySchema);

Then MyModel will use the tickets collection, not the ticket collection. For more details read the model docs.

Once we have our model, we can then instantiate it, and save it:

const instance = new MyModel();
instance.my.key = 'hello';
await instance.save();

Or we can find documents from the same collection

await MyModel.find({});

You can also findOne, findById, update, etc.

const instance = await MyModel.findOne({ /* ... */ });
console.log(instance.my.key); // 'hello'

For more details check out the docs.

Important! If you opened a separate connection using mongoose.createConnection() but attempt to access the model through mongoose.model('ModelName') it will not work as expected since it is not hooked up to an active db connection. In this case access your model through the connection you created:

const conn = mongoose.createConnection('your connection string');
const MyModel = conn.model('ModelName', schema);
const m = new MyModel();
await m.save(); // works

vs

const conn = mongoose.createConnection('your connection string');
const MyModel = mongoose.model('ModelName', schema);
const m = new MyModel();
await m.save(); // does not work b/c the default connection object was never connected

Embedded Documents

In the first example snippet, we defined a key in the Schema that looks like:

comments: [Comment]

Where Comment is a Schema we created. This means that creating embedded documents is as simple as:

// retrieve my model
const BlogPost = mongoose.model('BlogPost');

// create a blog post
const post = new BlogPost();

// create a comment
post.comments.push({ title: 'My comment' });

await post.save();

The same goes for removing them:

const post = await BlogPost.findById(myId);
post.comments[0].deleteOne();
await post.save();

Embedded documents enjoy all the same features as your models. Defaults, validators, middleware.

Middleware

See the docs page.

Intercepting and mutating method arguments

You can intercept method arguments via middleware.

For example, this would allow you to broadcast changes about your Documents every time someone sets a path in your Document to a new value:

schema.pre('set', function(next, path, val, typel) {
  // `this` is the current Document
  this.emit('set', path, val);

  // Pass control to the next pre
  next();
});

Moreover, you can mutate the incoming method arguments so that subsequent middleware see different values for those arguments. To do so, just pass the new values to next:

schema.pre(method, function firstPre(next, methodArg1, methodArg2) {
  // Mutate methodArg1
  next('altered-' + methodArg1.toString(), methodArg2);
});

// pre declaration is chainable
schema.pre(method, function secondPre(next, methodArg1, methodArg2) {
  console.log(methodArg1);
  // => 'altered-originalValOfMethodArg1'

  console.log(methodArg2);
  // => 'originalValOfMethodArg2'

  // Passing no arguments to `next` automatically passes along the current argument values
  // i.e., the following `next()` is equivalent to `next(methodArg1, methodArg2)`
  // and also equivalent to, with the example method arg
  // values, `next('altered-originalValOfMethodArg1', 'originalValOfMethodArg2')`
  next();
});

Schema gotcha

type, when used in a schema has special meaning within Mongoose. If your schema requires using type as a nested property you must use object notation:

new Schema({
  broken: { type: Boolean },
  asset: {
    name: String,
    type: String // uh oh, it broke. asset will be interpreted as String
  }
});

new Schema({
  works: { type: Boolean },
  asset: {
    name: String,
    type: { type: String } // works. asset is an object with a type property
  }
});

Driver Access

Mongoose is built on top of the official MongoDB Node.js driver. Each mongoose model keeps a reference to a native MongoDB driver collection. The collection object can be accessed using YourModel.collection. However, using the collection object directly bypasses all mongoose features, including hooks, validation, etc. The one notable exception that YourModel.collection still buffers commands. As such, YourModel.collection.find() will not return a cursor.

API Docs

Mongoose API documentation, generated using dox and acquit.

Related Projects

MongoDB Runners

Unofficial CLIs

Data Seeding

Express Session Stores

License

Copyright (c) 2010 LearnBoost <dev@learnboost.com>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.