Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Backbone.js sync via Socket.IO
Tag: v0.1.2

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


Storage-agnostic Backbone.js sync override and server notifications via Socket.IO.


npm install


On the server:

var http        = require('http'),
    backboneio  = require(''),
    app         = http.createServer();


var Backend = require('');
backboneio.listen(app, { mybackend: new Backend() });

On the client:

<!-- Include Underscore, Backbone -->

<script src="/"></script>
<script src="/"></script>

    var MyCollection = Backbone.Collection.extend({
        backend: 'mybackend'

Models in TestCollection will now be synced to mybackend.


When a model is synced with a particular backend, the backend will trigger events on collections (across multiple clients) that share the backend. For example, we could keep collections synced in realtime with the following event bindings:

var MyCollection = Backbone.Collection.extend({

    backend: 'mybackend',

    initialize: function() {
        var self = this;

        this.bind('backend:create', function(model) {
        this.bind('backend:update', function(model) {
        this.bind('backend:delete', function(model) {


Or use the provided shortcut:

backend: 'mybackend',

initialize: function() {

In addition to backend:create, backend:read, backend:update, and backend:delete events, a generic backend event is also triggered when a model is synced.

this.bind('backend', function(method, model) {
    // Method will be one of create, read, update, or delete

The event prefix backend is used by default but this can be customized by setting the event name on the server.

backboneio.listen(app, { mybackend: new Backend() }, { event: 'myevent' });


A backend is an object that exposes four functions, create, read, update, and delete, corresponding to the methods of Backbone.sync. Each function takes a model object and a callback. For example, a backend that interacts with a database might look something like this:

var MyBackend = {
    create: function(model, callback) {
        db.insert(model, function(err, record) {
            // The returned record must have an `id`
            // attribute defined.
            callback(err, record);

    read: function(model, callback) {
        if ( {
            // When an `id` is present, return single record
            db.findOne({ id: }, function(err, record) {
                callback(err, record);
        } else {
            // Otherwise return all records
            db.find({}, function(err, records) {
                callback(err, records);

    update: function(model, callback) {
        db.update({ id: }, model, function(err) {
            // Return the updated model
            callback(err, model);

    delete: function(model, callback) {
        db.delete({ id: }, function(err) {
            // Return the deleted model
            callback(err, model);

One can then use the custom backend like so:

backboneio.listen(app, { mybackend: MyBackend });

Further Customizations

Since the call to listen returns the Socket.IO object, it can be manipulated beyond the basics of Backbone.IO. Take a look at examples/auth.js, for example, to see how this can be leveraged to implement a custom authorization scheme.

Something went wrong with that request. Please try again.