Ruby

This module should effectively be able to spawn Rack, and thus Rails, applications.

HTTP

For Desaster, an HTTP request is nothing else than a Job to be executed, so this framework just
fits the best when it comes to fair load balancing your incoming HTTP requests over a large cluster.

This worker implements receiving HTTP requests, possibly terminating SSL, possibly passing
it to the designated master scheduler, to be then scheduled and passed to the actual backend
worker.

Speaking of our particular use-case, on a backend node, we might even optimize the communication path
a little further to combine it with the ruby glue code to actually handle our Rack/Passenger Rails requests.

API Bindings

You communicate via TCP/IP to the Desaster cluster, however, we at least provide
an access API for Ruby (1.8 and 1.9 compatible) and C++.