Go Circuit – Distributed Go Programming Framework

<a href="https://github.com/tumblr/gocircuit" rel="nofollow">https://github.com/tumblr/gocircuit</a>

For those who, like me, were looking for a more in-depth <i>"About"</i> page, the <i>"Big picture: problems and solutions"</i> link under <i>"Research"</i> is what you want:<p><a href="http://www.gocircuit.org/big.html" rel="nofollow">http://www.gocircuit.org/big.html</a><p>(also, to the maintainer: the "Ideal architecture" header at the bottom is on the wrong column)

Sounds like Go adding more Erlang style features. Off the top of my head, some nice things that Erlang lacks in that department might include:<p>* A bit more security by default. Erlang was built for something where they presumed they were walled off from bad stuff.<p>* Some kind of routing mechanism, so that you could have A connected to B, and B connected to C, and the system would be able to send messages from A to C. I have no idea if this is actually a good idea, as this is not the sort of thing I use Erlang for myself. But it seems like it might be cool.

<i>This application is temporarily over its serving quota. Please try again later.</i><p>Seems to be running on AppEngine by the look of it. AppEngine has the limits far too low for basic stuff like this, they should really re-look at their service offering if they want to actually compete in the market.

Can someone explain how `Spawn` ships the closure for execution to a remote host? I'm quite curious to know. I had a grep through the source, but I only found one [1] implementation of `Spawn` accepting a function as a parameter in the code base. This hides the true implementation, which I'm struggling to find. Any hints?<p>[1] <a href="https://github.com/tumblr/gocircuit/blob/master/src/circuit/use/circuit/bind.go#L84" rel="nofollow">https://github.com/tumblr/gocircuit/blob/master/src/circuit/...</a>

This looks like tumblr took their hand at making "netchan" (and more). Pretty interesting; I'll have to check this out. I like how they tried to make it similar to Erlang. However, the way they've organized the source isn't "go-get"able which is a pet peeve of mine.

Quick popularity like making it to the front page of HN, Reddit, Slashdot, etc. can become quite the curse when you're running a small app on App Engine. Of course, after throwing a few buckets of money down the well, you'll quickly learn to start optimizing for the platform. I don't know what this framework does, but it might be useful to link to a static page in the interim and then have people click through to your app.