Multi-database ORM: redis, mongodb, mysql, sqlite, postgres, neo4j, memory... Many databases, common API.
JavaScript CoffeeScript Shell
Pull request Compare This branch is 472 commits behind 1602:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


JugglingDB is cross-db ORM for nodejs, providing common interface to access most popular database formats. Currently supported are: mysql, sqlite3, postgres, couchdb, mongodb, redis, neo4j and js-memory-storage (yep, self-written engine for test-usage only). You can add your favorite database adapter, checkout one of the existing adapters to learn how, it's super-easy, I guarantee.

Jugglingdb also works on client-side (using WebService and Memory adapters), which allows to write rich client-side apps talking to server using JSON API.


npm install jugglingdb

plus you should install appropriated adapter, for example for redis:

npm install jugglingdb-redis

check following list of available adapters

JugglingDB adapters

<!-- MongoDB -->
  <td><a href=""><img src="" alt="MongoDB" /></a> MongoDB</td>
  <td><a href="">jugglingdb/mongodb-adapter</a></td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>

<!-- MySQL -->
  <td><a href=""><img src="" style="vertical-align:middle"" alt="MySQL" /></a> MySQL</td>
  <td><a href="">jugglingdb/mysql</a></td>
  <td><a href="">dgsan</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>

<!-- CouchDB / nano -->
  <td><a href=""><img width="16" src="" style="vertical-align:middle"" alt="CouchDB" /></a> CouchDB / nano</td>
  <td><a href="">jugglingdb/nano-adapter</a></td>
  <td><a href="">Nicholas Westlake</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>

<!-- PostgreSQL -->
  <td><a href=""><img src="" style="vertical-align:middle"" alt="PostgreSQL" /></a> PostgreSQL</td>
  <td><a href="">jugglingdb/postgres-adapter</a></td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>

<!-- Redis -->
  <td><a href=""><img src="" alt="Redis" /></a> Redis</td>
  <td><a href="">jugglingdb-redis</a></td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>

<!-- SQLite -->
  <td><a href=""><img width="16" src="" style="vertical-align:middle"" alt="SQLite" /></a> SQLite</td>
  <td><a href="">jugglingdb/sqlite3-adapter</a></td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td><a href=""><img src="" alt="Build Status" /></a></td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td>Memory (bogus)</td>
  <td><a href="">Anatoliy Chakkaev</a></td>
  <td>built-in <i>TODO: move</i></td>
  <td><a href=""><strike>Anatoliy Chakkaev</strike></a> <u>/!\</u> Looking for
Database type Package name Maintainer Build status
Firebird Firebird jugglingdb-firebird Henri Gourvest


If you want to create your own jugglingdb adapter, you should publish your adapter package with name jugglingdb-ADAPTERNAME. Creating adapter is simple, check jugglingdb/redis-adapter for example. JugglingDB core exports common tests each adapter should pass, you could create your adapter in TDD style, check that adapter pass all tests defined in test/common_test.js.


var Schema = require('jugglingdb').Schema;
var schema = new Schema('redis', {port: 6379}); //port number depends on your configuration
// define models
var Post = schema.define('Post', {
    title:     { type: String, length: 255 },
    content:   { type: Schema.Text },
    date:      { type: Date,    default: },
    published: { type: Boolean, default: false, index: true }

// simplier way to describe model
var User = schema.define('User', {
    name:         String,
    bio:          Schema.Text,
    approved:     Boolean,
    joinedAt:     Date,
    age:          Number
}, {
    restPath: '/users' // tell WebService adapter which path use as API endpoint

// define any custom method
User.prototype.getNameAndAge = function () {
    return + ', ' + this.age;

// models also accessible in schema:

// setup relationships
User.hasMany(Post,   {as: 'posts',  foreignKey: 'userId'});
// creates instance methods:
// user.posts(conds)
// // like new Post({userId:});
// user.posts.create(data) // build and save

Post.belongsTo(User, {as: 'author', foreignKey: 'userId'});
// creates instance methods:
// -- getter when called with function
// -- sync getter when called without params
// -- setter when called with object

schema.automigrate(); // required only for mysql NOTE: it will drop User and Post tables

// work with models:
var user = new User; (err) {
    var post ={title: 'Hello world'});;

// or just call it as function (with the same result):
var user = User();;

// Common API methods

// just instantiate model
new Post
// save model (of course async)
// all posts
// all posts by user
Post.all({where: {userId:}, order: 'id', limit: 10, skip: 20});
// the same as prev
// get one latest post
Post.findOne({where: {published: true}, order: 'date DESC'}, cb);
// same as new Post({userId:});
// save as Post.create({userId:}, cb);
// find instance by id
User.find(1, cb)
// count instances
User.count([conditions, ]cb)
// destroy instance
// destroy all instances

// Setup validations
User.validatesPresenceOf('name', 'email')
User.validatesLengthOf('password', {min: 5, message: {min: 'Password is too short'}});
User.validatesInclusionOf('gender', {in: ['male', 'female']});
User.validatesExclusionOf('domain', {in: ['www', 'billing', 'admin']});
User.validatesNumericalityOf('age', {int: true});
User.validatesUniquenessOf('email', {message: 'email is not unique'});

user.isValid(function (valid) {
    if (!valid) {
        user.errors // hash of errors {attr: [errmessage, errmessage, ...], attr: ...}    


The following callbacks supported:

- afterInitialize
- beforeCreate
- afterCreate
- beforeSave
- afterSave
- beforeUpdate
- afterUpdate
- beforeDestroy
- afterDestroy
- beforeValidation
- afterValidation

Each callback is class method of the model, it should accept single argument: next, this is callback which should be called after end of the hook. Except afterInitialize because this method is syncronous (called after new Model).

Object lifecycle:

var user = new User;
// afterInitialize;
// beforeValidation
// afterValidation
// beforeSave
// beforeCreate
// afterCreate
// afterSave
// callback
user.updateAttribute('email', '', callback);
// beforeValidation
// afterValidation
// beforeUpdate
// afterUpdate
// callback
// beforeDestroy
// afterDestroy
// callback
User.create(data, callback);
// beforeValidate
// afterValidate
// beforeCreate
// afterCreate
// callback

Read the tests for usage examples: ./test/common_test.js Validations: ./test/validations_test.js

Your own database adapter

To use custom adapter, pass it's package name as first argument to Schema constructor:

var mySchema = new Schema('mycouch', {host:.., port:...});

In that case your adapter should be named as 'jugglingdb-mycouch' npm package.


Core of jugglingdb tests only basic features (database-agnostic) like validations, hooks and runs db-specific tests using memory storage. It also exports complete bucket of tests for external running. Each adapter should run this bucket (example from jugglingdb-redis):

var jdb = require('jugglingdb'),
Schema = jdb.Schema,
test = jdb.test;

var schema = new Schema(__dirname + '/..', {host: 'localhost', database: 1});

test(module.exports, schema);

Each adapter could add specific tests to standart bucket:'should do something special', function (test) {

Or it could tell core to skip some test from bucket:

test.skip('name of test case');

To run tests use this command:

npm test

Before running make sure you've installed package (npm install) and if you running some specific adapter tests, ensure you've configured database correctly (host, port, username, password).


If you have found a bug please write unit test, and make sure all other tests still pass before pushing code to repo.