Which is Better Node.js ORM Libraries?
mongoose vs typeorm vs sequelize vs knex vs bookshelf

1 Year
mongoosetypeormsequelizeknexbookshelfSimilar Packages:
What's Node.js ORM Libraries?

Node.js ORM (Object-Relational Mapping) libraries provide a way to interact with databases using object-oriented programming. They offer features like query building, data modeling, relationships, and transactions to simplify database operations. Choosing the right ORM library depends on factors like database compatibility, performance requirements, and developer preferences.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
mongoose2,845,97026,7792.71 MB2362 days agoMIT
typeorm1,846,94633,71720.4 MB2,4775 months agoMIT
sequelize1,713,00329,2642.9 MB9143 months agoMIT
knex1,607,67618,978874 kB1,1117 months agoMIT
bookshelf60,0046,345-2364 years agoMIT
Feature Comparison: mongoose vs typeorm vs sequelize vs knex vs bookshelf

Database Compatibility

  • mongoose: Mongoose is designed for MongoDB, a NoSQL database. It offers schema-based data modeling and validation tailored for MongoDB's document-oriented structure.
  • typeorm: TypeORM supports both SQL databases (MySQL, PostgreSQL, SQLite) and NoSQL databases like MongoDB. It allows developers to switch between relational and non-relational databases.
  • sequelize: Sequelize is compatible with multiple SQL databases like MySQL, PostgreSQL, SQLite, and MSSQL. It provides a consistent API for working with different database systems.
  • knex: Knex supports various SQL databases such as MySQL, PostgreSQL, SQLite, and Oracle. It provides a unified interface for interacting with different database systems.
  • bookshelf: Bookshelf primarily supports SQL databases like MySQL, PostgreSQL, and SQLite. It integrates with Knex.js to handle database connections and query building.

Performance

  • mongoose: Mongoose's schema-based approach can improve performance by enforcing data structure consistency and validation. It also supports features like indexing and population for efficient data retrieval.
  • typeorm: TypeORM's type-safe queries and relationships can help prevent runtime errors and improve performance by catching issues during development. It offers optimizations for query execution and data retrieval.
  • sequelize: Sequelize provides advanced query capabilities like eager loading, transactions, and migrations, which can enhance performance for complex applications. It offers optimizations for handling large datasets.
  • knex: Knex offers flexibility in query building and execution, allowing developers to optimize queries for performance. It provides control over query generation and execution.
  • bookshelf: Bookshelf is lightweight and focused on data modeling, which can lead to better performance for simple applications. However, it may lack some advanced features for optimizing complex queries.

Learning Curve

  • mongoose: Mongoose's schema-based approach may have a moderate learning curve for developers new to MongoDB or schema validation. It offers rich documentation and examples to help developers get started.
  • typeorm: TypeORM's TypeScript support and decorator-based syntax can be beneficial for developers familiar with TypeScript. It may have a moderate learning curve for those new to ORMs or TypeScript.
  • sequelize: Sequelize's comprehensive feature set and ORM conventions may result in a steeper learning curve for beginners. It requires understanding of ORM concepts like associations, migrations, and transactions.
  • knex: Knex's query builder syntax is straightforward and similar to raw SQL, making it easy for developers with SQL experience to transition. It requires a basic understanding of database concepts.
  • bookshelf: Bookshelf has a relatively low learning curve due to its simplicity and focus on data modeling. It is easy to get started with for developers familiar with JavaScript and SQL.

Community Support

  • mongoose: Mongoose has a strong community due to its popularity for MongoDB development. It offers a rich ecosystem of plugins, middleware, and community support for various use cases.
  • typeorm: TypeORM has a growing community with increasing adoption among TypeScript developers. It provides documentation, examples, and community plugins to support developers.
  • sequelize: Sequelize has a mature community with a history of active development and support. It is widely adopted in the Node.js community for SQL database interactions.
  • knex: Knex has a large and active community with extensive documentation, plugins, and community-contributed packages. It is widely used in the Node.js ecosystem for SQL query building.
  • bookshelf: Bookshelf has a smaller community compared to other ORM libraries, which may result in fewer resources and community plugins. It is maintained by the same team behind Knex.js.
How to Choose: mongoose vs typeorm vs sequelize vs knex vs bookshelf
  • mongoose: Choose Mongoose if you are working with MongoDB and need a schema-based solution for data modeling. Mongoose provides a rich set of features for defining schemas, validating data, and interacting with MongoDB.
  • typeorm: Choose TypeORM if you prefer a TypeScript-friendly ORM that supports both SQL and NoSQL databases. TypeORM provides decorators for defining entities, relationships, and queries in a type-safe manner.
  • sequelize: Choose Sequelize if you require a powerful ORM with support for multiple SQL databases. Sequelize offers features like migrations, transactions, and advanced query capabilities for building complex applications.
  • knex: Choose Knex if you need a flexible SQL query builder for Node.js. Knex supports multiple database systems and allows you to write raw SQL queries or use a query builder to interact with databases.
  • bookshelf: Choose Bookshelf if you prefer a simple and lightweight ORM that focuses on data modeling and relationships. It is built on top of Knex.js and provides a fluent API for defining models, associations, and queries.
Similar Npm Packages to mongoose

mongoose is a popular Object Data Modeling (ODM) library for MongoDB and Node.js. It provides a straightforward way to model your application data and interact with MongoDB databases using JavaScript objects. Mongoose simplifies the process of defining schemas, performing CRUD operations, and handling relationships between data.

When it comes to working with databases in Node.js applications, there are several alternatives to mongoose that offer similar functionalities. Here are a few alternatives:

  • bookshelf is a JavaScript ORM for Node.js that provides an easy way to interact with databases using models and relationships. It offers a simple API for querying and managing data.
  • sequelize is a powerful ORM for Node.js that supports multiple SQL databases such as MySQL, PostgreSQL, SQLite, and MSSQL. It provides a robust set of features for defining models, querying data, and handling transactions.
  • typeorm is an ORM that supports TypeScript and JavaScript (ES7, ES6, ES5). It works with various SQL databases and provides features like entity modeling, query building, and migrations.

For a detailed comparison of bookshelf, mongoose, sequelize, and typeorm, check out: Comparing bookshelf vs mongoose vs sequelize vs typeorm.

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

Find the API docs here, 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.