Awesome
Overview
Spinoff is a framework for writing distributed, fault tolerant and scalable applications in Python. <a href="http://travis-ci.org/eallik/spinoff" title="Spinoff on Travis-CI.org"><img src="https://secure.travis-ci.org/eallik/spinoff.png?branch=master" alt="<build status indicator on travis-ci.org/eallik/spinoff>"/></a>
Spinoff is based on the Actor Model and borrows from Akka (location transparency, actor references, etc) and Erlang (processes, nodename@hosthost style node references (not implemented yet)).
Spinoff has been built using Gevent and ZeroMQ for remoting.
Spinoff is currently under continuous development but is nevertheless usable for writing real applications—it can also be fault tolerant towards some of the bugs in its own code.
Hype
"anyway, spinoff is really super nice to play with all this stuff because it's cheap to write code in it it really shines at making quick prototypes"
...so let's hope one day there will be a testimonial here saying "it really shines at making production software".
Example
The following is only a very small "peek preview" style example of what the framework can do. More examples and full documentation will follow soon.
See spinoff/examples/example1.py
The example can be run using the following command:
$ spin spinoff.examples.example1.ExampleProcess
or
$ spin spinoff.examples.example1.ExampleProcess
Distributed Example (with Remoting)
See spinoff/examples/example2.py
The example can be run using the following commands:
$ spin -pid node1.pid -nid localhost:9700 spinoff.examples.example2.ExampleActor -name other
$ spin -pid node2.pid -nid localhost:9701 spinoff.examples.example2.ExampleProcess -using "other_actor='localhost:9700/other'"
Same Distributed Code without Remoting
The following example demonstrates how it's possible to run the same code, unmodified, in a single thread with no network/remoting involved whatsoever. It's an illustration of how actors (components) written using Spinoff are xagnostic of how they are wired to work with other actors and can thus be viewed as abstract components containing only pure domain logic and no low level transportation and topology details.
See spinoff/examples/example2_local.py
The example can be run using the following command:
bash $ spin spinoff.examples.example2_local.LocalApp
One might ask, then, what is the difference between remoting frameworks such as CORBA and Spinoff. The difference is that actors define clear boundaries where remoting could ever be used, as opposed to splitting a flow of tightly coupled logic into two nodes on the network, which, still providing valid output, can degrade in performance significantly. This is not to say that actors with location transparency suffer none of such issues but the extent to which the problem exists is, arguably, an order of magnitude lower.
Example HTTP server
See spinoff/examples/005_http.py
The example can be run using the following commands:
$ spin spinoff.examples.0005_http.Main