mongoose vs typeorm vs sequelize vs bookshelf
Node.js ORM Libraries
mongoosetypeormsequelizebookshelf类似的npm包:
Node.js ORM Libraries

Node.js ORM(对象关系映射)库用于简化与数据库的交互,使开发者能够使用JavaScript对象而不是SQL查询来操作数据库。ORM库提供了一种抽象层,使得数据模型与数据库表之间的映射变得简单,允许开发者专注于业务逻辑而不是底层数据访问细节。每个库都有其独特的设计理念和功能,适用于不同的使用场景和需求。

npm下载趋势
3 年
GitHub Stars 排名
统计详情
npm包名称
下载量
Stars
大小
Issues
发布时间
License
mongoose3,594,06027,4422.03 MB1953 天前MIT
typeorm2,899,25736,22620.8 MB4951 个月前MIT
sequelize2,222,97830,3202.91 MB1,00110 个月前MIT
bookshelf84,2716,365-2376 年前MIT
功能对比: mongoose vs typeorm vs sequelize vs bookshelf

数据库支持

  • mongoose:

    Mongoose专为MongoDB设计,提供了强大的数据建模和验证功能,能够轻松处理文档和集合。

  • typeorm:

    TypeORM支持多种SQL和NoSQL数据库,包括PostgreSQL、MySQL、SQLite和MongoDB,提供灵活的模型定义和查询功能。

  • sequelize:

    Sequelize支持多种SQL数据库,包括PostgreSQL、MySQL、MariaDB和SQLite,提供丰富的查询功能和关系管理。

  • bookshelf:

    Bookshelf支持多种SQL数据库,如PostgreSQL、MySQL和SQLite。它使用Knex.js作为查询构建器,允许开发者使用SQL语法进行复杂查询。

数据模型

  • mongoose:

    Mongoose提供Schema定义,允许开发者为数据模型定义字段类型、验证规则和默认值,确保数据的一致性和完整性。

  • typeorm:

    TypeORM支持使用装饰器定义模型,提供强类型支持,适合TypeScript开发者。它支持Active Record和Data Mapper两种模式,灵活性高。

  • sequelize:

    Sequelize支持丰富的模型定义,包括字段类型、验证、钩子和关系,能够轻松管理复杂的数据结构。

  • bookshelf:

    Bookshelf允许开发者使用JavaScript对象定义模型,支持继承和关系定义。它的模型定义简单直观,适合快速开发。

查询构建

  • mongoose:

    Mongoose提供了丰富的查询API,支持链式调用和聚合操作,能够轻松处理复杂的查询需求。

  • typeorm:

    TypeORM支持使用QueryBuilder构建复杂查询,提供灵活的查询选项和参数化查询,适合需要动态查询的应用。

  • sequelize:

    Sequelize提供强大的查询构建功能,支持链式调用、事务、关联查询和聚合函数,适合复杂的数据库操作。

  • bookshelf:

    Bookshelf使用Knex.js作为查询构建器,允许开发者使用链式调用构建复杂查询,支持原生SQL查询。

学习曲线

  • mongoose:

    Mongoose的学习曲线稍陡,尤其是在Schema定义和数据验证方面,但其强大的功能使得处理复杂数据结构变得容易。

  • typeorm:

    TypeORM的学习曲线较陡,尤其是对于不熟悉TypeScript的开发者,但其类型安全和灵活性使得它在大型项目中非常有用。

  • sequelize:

    Sequelize的学习曲线适中,提供了丰富的功能和文档,适合需要全面功能的开发者。

  • bookshelf:

    Bookshelf的学习曲线相对较平缓,适合需要快速上手的开发者。其API简单易懂,适合小型项目和快速开发。

社区支持

  • mongoose:

    Mongoose拥有活跃的社区和丰富的文档,开发者可以轻松找到解决方案和示例。

  • typeorm:

    TypeORM的社区正在快速增长,提供了丰富的文档和示例,适合希望使用TypeScript的开发者。

  • sequelize:

    Sequelize是一个成熟的ORM,拥有广泛的社区支持和大量的学习资源,适合新手和经验丰富的开发者。

  • bookshelf:

    Bookshelf的社区相对较小,但由于其基于Knex.js,开发者可以利用Knex.js的文档和社区资源。

如何选择: mongoose vs typeorm vs sequelize vs bookshelf
  • mongoose:

    选择Mongoose如果你正在使用MongoDB,并且需要一个功能强大的数据建模工具。Mongoose提供了丰富的Schema定义和验证功能,适合需要复杂数据结构的应用。

  • typeorm:

    选择TypeORM如果你希望使用TypeScript,并且需要一个支持Active Record和Data Mapper模式的ORM。TypeORM适合需要高度类型安全和灵活性的项目。

  • sequelize:

    选择Sequelize如果你需要一个功能全面的ORM,支持多种SQL数据库,并且希望使用Promise和async/await语法。Sequelize提供了强大的模型定义和关系管理功能,适合大型应用。

  • bookshelf:

    选择Bookshelf如果你需要一个轻量级的ORM,支持多种数据库,并且希望使用Promise和Knex.js的查询构建器。它适合需要灵活性和可扩展性的项目。

mongoose的README

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 9.0.0 was released on November 21, 2025. You can find more details on backwards breaking changes in 9.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:

Then install the mongoose package using your preferred package manager:

Using npm

npm install mongoose

Using pnpm

pnpm add mongoose

Using Yarn

yarn add mongoose

Using Bun

bun add 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.