Redis Oplog for Meteor

Redis Oplog is complete re-implementation of LiveQuery (commonly referred to as oplog tailing). Redis Oplog enables your application to control its reactive queries through Redis - rather than just respond to MongoDB's operation logs. It opens a new world into building fast, scalable, and reactive applications.

Redis Oplog is backwards compatible with LiveQuery, so there won't be any change in how you use Meteor. It's also incrementally adoptable and should work flawlessly with-in your current setup.

Redis Oplog is intended for applications that are scaling to 1000 concurrent clients and beyond. However, it can also be beneficial for smaller applications, as it could trim CPU usage, save you hosting expenses, and enable you to fine-tune your reactive queries.

To summarize, Redis Oplog:

is backwards compatible with LiveQuery
can be incrementally adopted alongside LiveQuery
scales Meteor's reactive queries horizontally
lets you control your reactive queries
saves costs by lowering CPU usage

How to Use

First, add Redis Oplog to your app:

meteor remove insecure
meteor add disable-oplog
meteor add cultofcoders:redis-oplog

Second, configure the package via settings.json:

{
  // ...
  "redisOplog": {
    "redis": {
      "port": 6379,
      "host": "127.0.0.1"
    },
    "mutationDefaults": {
        "optimistic": false, // Does not to a sync processing on the diffs
        "pushToRedis": true  // Pushes to Redis the changes
    }
    "debug": false,                 // Will show timestamp and activity of redis-oplog.
    "overridePublishFunction": true // Will patch Meteor.publish to become Meteor.publishWithRedis
  }
}

Finally, run your application:

meteor run --settings settings.json

Note: If you use any packages that initialize collections, including local ones, make sure that cultofcoders:redis-oplog loads first. See the Load Order document for more information.

msavin/redis-oplog

Redis Oplog for Meteor

How to Use

Further Reading