Pebble is real time event streams / pub sub done simply.
- Cleaner in terms of code
- Simpler to run (One process, versus many)
- Easy to extend (based on a simple publisher model)
With the whole goal of making real time event streams (pulling events from external sources) as simple as possible.
Originally built for Rails Rumble 2010 like I built prior versions for earlier rumbles.
Writing a Publisher
Publishers are just the general idea of a configurable item which can push things to the notifications list. For example, to implement a simple publisher, you can do (in CoffeeScript):
Base = require('pebble/base).Base class MyPublisher extends Base name: "my-publisher" setup: -> # Called automatically. stored_name = @get "name" # gets name in the my-publisher key in the configuration setInterval((=> @emit some: "data" ), 10000)
You define a setup method that starts doing processing, configure a name (and optionally,
for events and
configNamespace for the configuration json namespace). This simple yet flexible architecture
makes it possible to build a wide variety of publishers.
Pebble uses a standard
config.json file which uses nested keys according to:
- Pebble Settings (
- Redis settings (
- Publisher settings (either the publisher name or the
configNamespacevalue on a given publisher).
An example of this can be seen in the
config.example.json file which contains all options.
Please note that most options are optional.
Lastly, in the case of the following, they can also be overridden by an environment variable:
The Public JavasScript Portion
Please note the public portion can be found in
public/ and that
your application uses Pebble. It'd be pretty simple to port it to use
something other than jQuery but that is left as an exercise for the reader.
To develop pebble, you'll also need to install coffee-script via:
npm install coffee-script