Freebase is an attempt at getting the same kind of functionality that firebase offers, but it is free. It is a bit different from firebase in terms of it being a searchable key/value store, instead of arranging the data like one big json tree, like firebase does...
Firebase is fricking awesome - but sometimes priced a little out of the reach of certain projects, but if you have the money to throw at it, it is well worth investigating.
The aim of this framework however is to create an http/json api that sits on top of a mongo backend as the server, which also has pub/sub baked in - so you can subscribe to changes in the data via the client - which can be used from a browser thanks to browserify, or from a node program, depending on how it is initialized.
Technologies used: Freebase uses faye for its pub/sub framework and mongo or nedb depending on the mode it is running in as its data store, the API uses connect, the client uses jquery or request.js depending on whether it is running in the browser.
The system uses jwt to secure session state between calls.
This is the easiest setup, as the system uses nedb to store data internally, so you dont need mongo or redis running on your machine. You can just spin up an instance and start pushing data to it and listening for changes via the client.
- NB - the search functionality works slightly differently in embedded mode, $all is not supported, and nested columns like data.firstname dont work, when you try and limit the columns returned - you'll see what I mean if you look at the tests *
You can specify how many worker processes you want the system to use, so we can scale to multicore machines. You need a redis instance and a mongo instance for this mode, this is because Faye uses it's redis engine to keep state across clustered instances of the Freebase worker process.
The system runs as a single process, but still needs a mongo db instance running for storing data.
Freebase stores its data in a collection called 'freebase' by default on your mongodb. The freebase system is actually built to be a module, this is because the idea is that you will be able to initialize a server in your own code, and possibly attach your own plugins to various system events. So the requirements and installation instructions show you how to reference freebase and write the code that starts the instance up. This won't be a tremendously detailed document - so please do spelunk and get involved.
You need NodeJS and NPM of course, you also need to know how node works (as my setup instructions are pretty minimal)
You need to install mocha to run the tests, ie: sudo npm install mocha -g --save
If you want to run in cluster mode, you need to install Redis and have it up and running, on its standard port: 6379
If you want to run in cluster or single process mode, you need to install Mongo and have it up and running on its standard port: 27017
You can just clone this repository, then run "npm install" and then run "mocha test/e2e_test" to see how things work, there are 17 unit tests there that execute against freebase service running in embedded mode, they should all pass...
But if you want to run your own service do the following:
Create a directory you want to run your freebase in, create a node application in it - with some kind of main.js and a package.json
I havent had the time to join npm yet, so add the following dependancy to your package.json:
"dependencies": {
"freebase": "git+https://github.com/southbite/freebase.git"
}To get the latest freebase files run: npm install
In node_modules/freebase/test in your folder, the e2e_test.js script demonstrates the server and client interactions shown in the following code snippets
var freebase = require('freebase')
var service = freebase.service;
//Embedded mode (no external databases necessary):
service.initialize({services:{
auth:{
authTokenSecret:'a256a2fd43bf441483c5177fc85fd9d3',
systemSecret:test_secret
},
data:{
mode:'embedded'
}
}}, function(e){
callback(e);
});
//Cluster mode (needs redis and mongo):
service.initialize({mode:'cluster', size:2, port:testport, services:{
auth:{authTokenSecret:'a256a2fd43bf441483c5177fc85fd9d3',
systemSecret:test_secret}
}}, function(e){
callback(e);
});
//single process mode
service.initialize({port:testport, services:{
auth:{
authTokenSecret:'a256a2fd43bf441483c5177fc85fd9d3',
systemSecret:test_secret
},
data:{}
}}, function(e){
callback(e);
});In your console, go to your application folder and run node main your server should start up and be listening on your port of choice.
Using node:
var freebase = require('freebase');
var freebase_client = freebase.client;
var my_client_instance;
freebase_client.newClient({host:'localhost',
port:80,
secret:'my test secret'}, function(e, my_client_instance){
//if no e, then you have been passed back a client in the client variable
if (!e)
my_client_instance.get...To use the browser client, make sure the server is running, and reference the client javascript with the url pointing to the running server instances port and ip address like so:
<script type="text/javascript" src="http://localhost:80/browser_client"></script>
<script>
//Thanks to the magic of browserify.org the browser client works exactly the same way as what the node client does, and can immediately be referenced like this:
FreebaseBrowserClient.newClient({host:'localhost', port:80, secret:'my test secret'}, function(e, my_client_instance){
if (!e){
//instance.get...
//instance.set...
//instance.on...
}
});
</script>Puts the json in the branch e2e_test1/testsubscribe/data, creates the branch if it does not exist
my_client_instance.set('e2e_test1/testsubscribe/data', //the path you want to push your data to
{property1:'property1',property2:'property2',property3:'property3'}, //your data
{merge:true}, //options - can be null
function(e, result){
if (!e){
//successful
console.log(result.payload);//payload is an object with the result with an _id and containing a [data] property with yr uploaded dataNB - by setting the option merge:true, the data at the end of the path is not overwritten by your json, it is rather merged with the data in your json, overwriting the fields you specify in your set data, but leaving the fields that are already at that branch.
Posts your data to a collection that lives at the end of the specified branch (creates the collection if it doesnt exist), the getChild method will fetch your data back
my_client_instance.setChild('e2e_test1/testsubscribe/data/collection', {property1:'post_property1',property2:'post_property2'}, function(e, results){
if (!e){
//the child method returns a child in the collection with a specified id
my_client_instance.getChild('e2e_test1/testsubscribe/data/collection', results.payload._id, function(e, results){Posts your data to a unique path starting with the path you passed in as a parameter
my_client_instance.setSibling('e2e_test1/siblings', {property1:'sib_post_property1',property2:'sib_post_property2'}, function(e, results){
//you would get all siblings by querying the path e2e_test1/siblings*Gets the data living at the specified branch, gets the whole collection if the data is a collection, see the child method (above) for getting a specific item from a collection
my_client_instance.get('e2e_test1/testsubscribe/data',
null, //options
function(e, results){
//results is your data
console.log(results.payload.length);//payload is now an array containing all the results for your get, get can also use a wildcard * in the path ie. publisherclient.get('e2e_test1/testsubscribe/data*'...*You can also use wildcards, gets all items with the path starting e2e_test1/testsubscribe/data *
my_client_instance.get('e2e_test1/testsubscribe/data*',
null,
function(e, results){
//results is your data
console.log(results.payload.length);//payload is now an array containing all the results for your get, get can also use a wildcard * in the path ie. publisherclient.get('e2e_test1/testsubscribe/data*'...*You can also just get paths and ids, without data *
my_client_instance.getPaths('e2e_test1/testwildcard/*', function(e, results){You can pass mongo style search parameters to look for data sets within specific key ranges
parameters1 = {
criteria:{
$or: [ {"data.regions": { $in: ['North','South','East','West'] }},
{"data.towns": { $in: ['North.Cape Town', 'South.East London'] }},
{"data.categories": { $in: ["Action","History" ] }}],
"data.keywords": {$in: ["bass", "Penny Siopis" ]}
},
fields:{"data":1},
sort:{"data.field1":1},
limit:1
}
my_client_instance.search('/e2e_test1/testsubscribe/data/complex*', parameters1, function(e, search_result){Deletes the data living at the specified branch, if a child_id is specified, the child from the collection at the end of the branch is deleted
my_client_instance.remove('/e2e_test1/testsubscribe/data/delete_me', null, function(e, result){
if (!e)
//your item was deleted, result.payload is an object that lists the amount of objects deleted*Deletes a child from an array living at a branch *
//first we put
my_client_instance.setChild('/e2e_test1/testsubscribe/data/catch_all_array', {property1:'property1',property2:'property2',property3:'property3'}, function(e, post_result){
if (!e){
//your item was added to a collection, now remove it
my_client_instance.removeChild('/e2e_test1/testsubscribe/data/catch_all_array', post_result.payload._id, function(e, del_ar_result){
You can listen to any PUT, POST and DELETE events happeneing in your data - you can specifiy a path you want to listen on or you can listen to all PUT, POST and DELETE using a catch-all listener
Specific listener:
my_client_instance.on('/e2e_test1/testsubscribe/data/delete_me', //the path you are listening on
'DELETE', //either PUT,POST,DELETE
1, //how many times you want your listener event handler to fire - in this case your listener function will only fire once
function(e, message){ //your listener event handlerCatch all listener:
my_client_instance.onAll(function(e, message){
//message consists of action property - POST,PUT, DELETE
//and payload property - the actual data that got PUT, POSTED - or the _id of the data that got DELETED
}, function(e){*You can do a set command and specify that you want to tag the data at the end of the path (or the data that is created as a result of the command), tagging will take a snapshot of the data as it currently stands, and will save the snapshot to a path that starts with the path you specify, and a '/' with the tag you specify at the end *
var randomTag = require('shortid').generate();
my_client_instance.set('e2e_test1/test/tag', {property1:'property1',property2:'property2',property3:'property3'}, {tag:randomTag}, function(e, result){