What is Beehive?



This will start beehive on your local machine with the root /tmp/beehive. If you want to use a different directory, (such as something less transient like ~/beehive_data) run:

export BEEHIVE_HOME=~/beehive_data

When starting beehive in a non-dev mode, the beehive root will default to /var/lib/beehive.

Running tests

 make test

Make sure you have ruby gems rack and thin installed. Various tests depend up them, and tests likely won't complete properly without them.

How it works

The incredibly basic architecture diagram of beehive looks like:

Distributed Routing layer
  |         |         |    
Backend   Backend   Backend
  |         |         |    
Storage   Storage   Storage

The distributed routing layer, written in erlang uses Mnesia, the distributed database management system intelligently routes requests across the bees. The router currently can handle http requests. Because Beehive was written with the intention of being extensible it can be extensible to other protocols.

It handles pending connections seamlessly and allows for streaming connections. It also keeps track of statistical data available through a web interface. The router itself has a RESTful interface for adding bees, which don't even need to sit inside the Beehive network. This can be useful for putting the router in front of a personal cluster (such as Eucalyptus) and expanding to the cloud environment (such as EC2) without having to change a line of code.

Beehive keeps track of the available bees for the known applications.

Beehive has an event system that allows for notifications along the system in a nonblocking manner. This way system events, statistic gathering log events can all be handled without affecting the performance of the router, which is tuned for speed.

For more information about each particular part of the project, there are READMEs in each of the appropriate directories.


Note on Patches/Pull Requests


Copyright (c) 2010 Ari Lerner. See LICENSE for details.