For something more Erlang:ish (but better), see the Flow Based Programming implementation by Vladimir Sibirov, GoFlow: https://github.com/trustmaster/goflow htt

For something more Erlang:ish (but better), see the Flow Based Programming implementation by Vladimir Sibirov, GoFlow: https://github.com/trustmaster/goflow https://github.com/trustmaster/goflow . It lets you give your components names, and the inports of the components are somewhat analogous to Erlang inboxes as far as I can tell. But then it improves on the Erlang actor/mailbox concept by keeping the "wiring" of the connections between boxes completely separated from their implementation, which lets you change the data flow much more easily (hook in a monitor, logging facility, and extra test mock or whatever ... it is crazily powerful when you start to think about it!). GoFlow is of course not the only FBP implementation, but a Go implementation makes quite some sense I think. If you wonder what the Erlang creator (Joe Armstrong) thinks about FBP, you can find his comments on it here: http://programming.oreilly.com/2013/10/transformative-programming.html http://programming.oreilly.com/2013/10/transformative-progra... (He's considering implementing one in Erlang :) )