bookshelf vs knex vs sequelize vs waterline
Node.js ORM Libraries
bookshelfknexsequelizewaterlineSimilar Packages:

Node.js ORM Libraries

Node.js ORM (Object-Relational Mapping) libraries provide developers with a way to interact with databases using JavaScript objects instead of SQL queries. They abstract the database interactions, allowing for easier management of data models and relationships. Each library has its own approach to handling database operations, providing varying levels of abstraction, flexibility, and features that cater to different project needs.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
bookshelf06,357-2386 years agoMIT
knex020,267915 kB71124 days agoMIT
sequelize030,3552.91 MB1,0242 months agoMIT
waterline05,3931.3 MB34-MIT

Feature Comparison: bookshelf vs knex vs sequelize vs waterline

Abstraction Level

  • bookshelf:

    Bookshelf provides a moderate level of abstraction, allowing developers to define models and relationships easily while still giving access to raw SQL queries through Knex. This makes it suitable for those who want simplicity without losing control.

  • knex:

    Knex offers a low level of abstraction, functioning primarily as a SQL query builder. It allows developers to write SQL queries directly, giving them full control over the database interactions without the overhead of an ORM.

  • sequelize:

    Sequelize provides a high level of abstraction, allowing developers to work with models, associations, and migrations without needing to write raw SQL. This can speed up development but may obscure some database interactions.

  • waterline:

    Waterline offers a moderate to high level of abstraction, focusing on a simple API for data access while supporting multiple database types. It abstracts the underlying database interactions but can be less flexible than Knex.

Learning Curve

  • bookshelf:

    Bookshelf has a gentle learning curve, especially for those already familiar with Knex. Its straightforward API and documentation make it accessible for beginners while still offering advanced features for experienced developers.

  • knex:

    Knex has a low learning curve for those familiar with SQL, as it allows for writing raw SQL queries. However, it may require additional effort for developers new to SQL or those expecting a more abstracted ORM experience.

  • sequelize:

    Sequelize has a steeper learning curve due to its extensive feature set and conventions. Developers need to understand its model definitions, associations, and migration strategies, which can be overwhelming for newcomers.

  • waterline:

    Waterline has a moderate learning curve, particularly for those familiar with Sails.js. Its API is designed to be simple, but understanding its abstraction over different databases may take some time.

Performance

  • bookshelf:

    Bookshelf's performance is generally good for most applications, but it can be affected by the complexity of relationships and the number of queries made. Developers can optimize performance by carefully structuring their models and queries.

  • knex:

    Knex is highly performant as it allows for raw SQL queries, enabling developers to optimize their queries for specific use cases. However, performance depends on the quality of the SQL written by the developer.

  • sequelize:

    Sequelize can introduce some overhead due to its abstraction layer, which may impact performance in highly complex queries. However, it provides features like query optimization and caching to help mitigate this.

  • waterline:

    Waterline's performance can vary based on the underlying database and the complexity of the data interactions. While it simplifies data access, it may not be as performant as raw SQL queries in Knex.

Extensibility

  • bookshelf:

    Bookshelf is extensible through its plugin system, allowing developers to add custom functionality or modify existing features. This makes it adaptable for various project needs.

  • knex:

    Knex is highly extensible, allowing developers to create custom query builders and plugins. Its flexibility makes it suitable for a wide range of applications and database interactions.

  • sequelize:

    Sequelize supports extensibility through hooks and custom methods, enabling developers to add functionality to models and queries. This allows for a tailored experience based on specific application requirements.

  • waterline:

    Waterline is designed to be extensible, particularly within the Sails.js framework. Developers can create custom adapters to support additional databases or modify existing behavior.

Community and Support

  • bookshelf:

    Bookshelf has a smaller community compared to Sequelize, but it is well-documented and has a dedicated user base. Support can be found through GitHub and community forums.

  • knex:

    Knex has a large and active community, providing extensive documentation and numerous resources for troubleshooting and learning. This makes it easier to find help and examples.

  • sequelize:

    Sequelize boasts a large community and extensive documentation, making it one of the most popular ORMs in the Node.js ecosystem. This results in a wealth of resources, tutorials, and community support.

  • waterline:

    Waterline has a smaller community, primarily focused around the Sails.js framework. While documentation is available, it may not be as extensive as that of the other libraries.

How to Choose: bookshelf vs knex vs sequelize vs waterline

  • bookshelf:

    Choose Bookshelf if you prefer a simple, lightweight ORM that is built on top of Knex.js, providing a straightforward way to work with relational data and supports features like relations, virtuals, and pagination.

  • knex:

    Choose Knex if you need a flexible SQL query builder that allows for raw SQL queries and supports multiple database types. It is ideal for developers who want more control over their queries and prefer to write SQL directly while still benefiting from a fluent API.

  • sequelize:

    Choose Sequelize if you require a full-featured ORM with extensive support for associations, transactions, and migrations. It is suitable for complex applications where you need a robust solution with a rich set of features and built-in support for various database dialects.

  • waterline:

    Choose Waterline if you are working with the Sails.js framework or need a data access layer that supports multiple database types with a simple API. It is designed for easy integration with Sails and provides a more abstracted approach to data management.

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.