bookshelf vs knex vs sequelize vs typeorm
Node.js ORM Libraries
bookshelfknexsequelizetypeormSimilar Packages:

Node.js ORM Libraries

Node.js ORM libraries provide developers with an abstraction layer for interacting with databases, allowing them to work with database records as JavaScript objects. These libraries facilitate the management of database queries, relationships, and migrations, enhancing productivity and code maintainability. Each library has its unique features and design philosophies, catering to different project requirements and developer preferences.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
bookshelf06,365-2386 years agoMIT
knex020,245953 kB7092 days agoMIT
sequelize030,3552.91 MB1,02019 days agoMIT
typeorm036,41120.8 MB5214 months agoMIT

Feature Comparison: bookshelf vs knex vs sequelize vs typeorm

Database Support

  • bookshelf:

    Bookshelf supports various SQL databases through Knex.js, including PostgreSQL, MySQL, and SQLite, making it versatile for different project needs.

  • knex:

    Knex is primarily a SQL query builder that supports multiple databases such as PostgreSQL, MySQL, SQLite, and Oracle, allowing developers to write database-agnostic queries.

  • sequelize:

    Sequelize supports a wide range of SQL databases including PostgreSQL, MySQL, MariaDB, SQLite, and Microsoft SQL Server, providing a robust solution for diverse database environments.

  • typeorm:

    TypeORM supports various SQL databases like MySQL, PostgreSQL, MariaDB, SQLite, and Microsoft SQL Server, and also offers support for MongoDB, making it a flexible choice for different database types.

Learning Curve

  • bookshelf:

    Bookshelf has a relatively low learning curve, especially for those familiar with Knex.js, as it provides a simple API for defining models and relationships without overwhelming complexity.

  • knex:

    Knex has a moderate learning curve, as it requires understanding SQL syntax and query building, but its flexibility allows developers to gradually learn as they build more complex queries.

  • sequelize:

    Sequelize has a steeper learning curve due to its extensive feature set and conventions, but it offers comprehensive documentation and examples to help new users get started.

  • typeorm:

    TypeORM has a moderate to steep learning curve, particularly for those unfamiliar with TypeScript or decorators, but it provides a rich set of features that can be very beneficial for complex applications.

Extensibility

  • bookshelf:

    Bookshelf is extensible through plugins and custom model methods, allowing developers to tailor the ORM to their specific needs without significant overhead.

  • knex:

    Knex is highly extensible, allowing developers to create custom query builders and plugins, making it suitable for projects that require unique database interactions.

  • sequelize:

    Sequelize offers a variety of hooks and lifecycle events that allow for extensive customization and extensibility, enabling developers to implement complex business logic easily.

  • typeorm:

    TypeORM provides a robust extensibility model with decorators, custom repositories, and event listeners, allowing developers to create highly customized data models and interactions.

Performance

  • bookshelf:

    Bookshelf's performance is generally good for most applications, but it may not be as optimized for large-scale applications compared to more complex ORMs due to its simplicity.

  • knex:

    Knex is designed for performance, allowing developers to write optimized SQL queries directly, which can lead to better performance in high-load scenarios.

  • sequelize:

    Sequelize provides good performance for most applications, but its extensive feature set can introduce overhead. Proper indexing and query optimization are essential for maintaining performance.

  • typeorm:

    TypeORM is optimized for performance, particularly in TypeScript applications, but it can introduce some overhead with its advanced features. Proper configuration and usage patterns can help mitigate performance issues.

Community and Support

  • bookshelf:

    Bookshelf has a smaller community compared to others, but it benefits from the Knex.js community for support and resources.

  • knex:

    Knex has a strong community and is widely used, providing ample resources, documentation, and community support for developers.

  • sequelize:

    Sequelize boasts a large and active community, with extensive documentation, tutorials, and third-party resources available, making it easy to find help and examples.

  • typeorm:

    TypeORM has a growing community, especially among TypeScript developers, with good documentation and community support, although it may not be as large as Sequelize's.

How to Choose: bookshelf vs knex vs sequelize vs typeorm

  • bookshelf:

    Choose Bookshelf if you prefer a simple and lightweight ORM that is built on top of Knex.js, providing a straightforward way to manage relations and models without the complexity of a full-fledged ORM.

  • knex:

    Select Knex if you need a flexible SQL query builder that allows you to write raw SQL queries while still providing some ORM-like features. It's ideal for projects where you want fine-grained control over SQL syntax and database interactions.

  • sequelize:

    Opt for Sequelize if you need a feature-rich ORM that supports multiple SQL dialects, offers a wide range of built-in functionalities like migrations, validations, and associations, and has a strong community and documentation for support.

  • typeorm:

    Choose TypeORM if you are working with TypeScript and need an ORM that fully integrates with it, offering decorators and a powerful entity management system. It's suitable for complex applications that require advanced features like lazy loading and caching.

README for bookshelf

bookshelf.js

NPM Version Build Status Dependency Status devDependency Status

Bookshelf is a JavaScript ORM for Node.js, built on the Knex SQL query builder. It features both Promise-based and traditional callback interfaces, transaction support, eager/nested-eager relation loading, polymorphic associations, and support for one-to-one, one-to-many, and many-to-many relations.

It is designed to work with PostgreSQL, MySQL, and SQLite3.

Website and documentation. The project is hosted on GitHub, and has a comprehensive test suite.

Introduction

Bookshelf aims to provide a simple library for common tasks when querying databases in JavaScript, and forming relations between these objects, taking a lot of ideas from the Data Mapper Pattern.

With a concise, literate codebase, Bookshelf is simple to read, understand, and extend. It doesn't force you to use any specific validation scheme, and provides flexible, efficient relation/nested-relation loading and first-class transaction support.

It's a lean object-relational mapper, allowing you to drop down to the raw Knex interface whenever you need a custom query that doesn't quite fit with the stock conventions.

Installation

You'll need to install a copy of Knex, and either mysql, pg, or sqlite3 from npm.

$ npm install knex
$ npm install bookshelf

# Then add one of the following:
$ npm install pg
$ npm install mysql
$ npm install sqlite3

The Bookshelf library is initialized by passing an initialized Knex client instance. The Knex documentation provides a number of examples for different databases.

// Setting up the database connection
const knex = require('knex')({
  client: 'mysql',
  connection: {
    host     : '127.0.0.1',
    user     : 'your_database_user',
    password : 'your_database_password',
    database : 'myapp_test',
    charset  : 'utf8'
  }
})
const bookshelf = require('bookshelf')(knex)

// Defining models
const User = bookshelf.model('User', {
  tableName: 'users'
})

This initialization should likely only ever happen once in your application. As it creates a connection pool for the current database, you should use the bookshelf instance returned throughout your library. You'll need to store this instance created by the initialize somewhere in the application so you can reference it. A common pattern to follow is to initialize the client in a module so you can easily reference it later:

// In a file named, e.g. bookshelf.js
const knex = require('knex')(dbConfig)
module.exports = require('bookshelf')(knex)

// elsewhere, to use the bookshelf client:
const bookshelf = require('./bookshelf')

const Post = bookshelf.model('Post', {
  // ...
})

Examples

Here is an example to get you started:

const knex = require('knex')({
  client: 'mysql',
  connection: process.env.MYSQL_DATABASE_CONNECTION
})
const bookshelf = require('bookshelf')(knex)

const User = bookshelf.model('User', {
  tableName: 'users',
  posts() {
    return this.hasMany(Posts)
  }
})

const Post = bookshelf.model('Post', {
  tableName: 'posts',
  tags() {
    return this.belongsToMany(Tag)
  }
})

const Tag = bookshelf.model('Tag', {
  tableName: 'tags'
})

new User({id: 1}).fetch({withRelated: ['posts.tags']}).then((user) => {
  console.log(user.related('posts').toJSON())
}).catch((error) => {
  console.error(error)
})

Official Plugins

  • Virtuals: Define virtual properties on your model to compute new values.
  • Case Converter: Handles the conversion between the database's snake_cased and a model's camelCased properties automatically.
  • Processor: Allows defining custom processor functions that handle transformation of values whenever they are .set() on a model.

Community plugins

  • bookshelf-cascade-delete - Cascade delete related models on destroy.
  • bookshelf-json-columns - Parse and stringify JSON columns on save and fetch instead of manually define hooks for each model (PostgreSQL and SQLite).
  • bookshelf-mask - Similar to the functionality of the {@link Model#visible} attribute but supporting multiple scopes, masking models and collections using the json-mask API.
  • bookshelf-schema - A plugin for handling fields, relations, scopes and more.
  • bookshelf-signals - A plugin that translates Bookshelf events to a central hub.
  • bookshelf-paranoia - Protect your database from data loss by soft deleting your rows.
  • bookshelf-uuid - Automatically generates UUIDs for your models.
  • bookshelf-modelbase - An alternative to extend Model, adding timestamps, attribute validation and some native CRUD methods.
  • bookshelf-advanced-serialization - A more powerful visibility plugin, supporting serializing models and collections according to access permissions, application context, and after ensuring relations have been loaded.
  • bookshelf-plugin-mode - Plugin inspired by the functionality of the {@link Model#visible} attribute, allowing to specify different modes with corresponding visible/hidden fields of model.
  • bookshelf-secure-password - A plugin for easily securing passwords using bcrypt.
  • bookshelf-default-select - Enables default column selection for models. Inspired by the functionality of the {@link Model#visible} attribute, but operates on the database level.
  • bookshelf-ez-fetch - Convenient fetching methods which allow for compact filtering, relation selection and error handling.
  • bookshelf-manager - Model & Collection manager to make it easy to create & save deep, nested JSON structures from API requests.

Support

Have questions about the library? Come join us in the #bookshelf freenode IRC channel for support on knex.js and bookshelf.js, or post an issue on Stack Overflow.

Contributing

If you want to contribute to Bookshelf you'll usually want to report an issue or submit a pull-request. For this purpose the online repository is available on GitHub.

For further help setting up your local development environment or learning how you can contribute to Bookshelf you should read the Contributing document available on GitHub.

F.A.Q.

Can I use standard node.js style callbacks?

Yes, you can call .asCallback(function(err, resp) { on any database operation method and use the standard (err, result) style callback interface if you prefer.

My relations don't seem to be loading, what's up?

Make sure to check that the type is correct for the initial parameters passed to the initial model being fetched. For example new Model({id: '1'}).load([relations...]) will not return the same as new Model({id: 1}).load([relations...]) - notice that the id is a string in one case and a number in the other. This can be a common mistake if retrieving the id from a url parameter.

This is only an issue if you're eager loading data with load without first fetching the original model. new Model({id: '1'}).fetch({withRelated: [relations...]}) should work just fine.

My process won't exit after my script is finished, why?

The issue here is that Knex, the database abstraction layer used by Bookshelf, uses connection pooling and thus keeps the database connection open. If you want your process to exit after your script has finished, you will have to call .destroy(cb) on the knex property of your Bookshelf instance or on the Knex instance passed during initialization. More information about connection pooling can be found over at the Knex docs.

How do I debug?

If you pass debug: true in the options object to your knex initialize call, you can see all of the query calls being made. You can also pass that same option to all methods that access the database, like model.fetch() or model.destroy(). Examples:

// Turning on debug mode for all queries
const knex = require('knex')({
  debug: true,
  client: 'mysql',
  connection: process.env.MYSQL_DATABASE_CONNECTION
})
const bookshelf = require('bookshelf')(knex)

// Debugging a single query
new User({id: 1}).fetch({debug: true, withRelated: ['posts.tags']}).then(user => {
  // ...
})

Sometimes you need to dive a bit further into the various calls and see what all is going on behind the scenes. You can use node-inspector, which allows you to debug code with debugger statements like you would in the browser.

Bookshelf uses its own copy of the bluebird Promise library. You can read up here for more on debugging Promises.

Adding the following block at the start of your application code will catch any errors not otherwise caught in the normal Promise chain handlers, which is very helpful in debugging:

process.stderr.on('data', (data) => {
  console.log(data)
})

How do I run the test suite?

See the CONTRIBUTING document on GitHub.

Can I use Bookshelf outside of Node.js?

While it primarily targets Node.js, all dependencies are browser compatible, and it could be adapted to work with other javascript environments supporting a sqlite3 database, by providing a custom Knex adapter. No such adapter exists though.

Which open-source projects are using Bookshelf?

We found the following projects using Bookshelf, but there can be more:

  • Ghost (A blogging platform) uses bookshelf. [Link]
  • Soapee (Soap Making Community and Resources) uses bookshelf. [Link]
  • NodeZA (Node.js social platform for developers in South Africa) uses bookshelf. [Link]
  • Sunday Cook (A social cooking event platform) uses bookshelf. [Link]
  • FlyptoX (Open-source Node.js cryptocurrency exchange) uses bookshelf. [Link]
  • And of course, everything on here use bookshelf too.