goodboy

I'm kind of about "zero pump" these days; a project should either surface because it's good or die. Maybe that's a bit extreme though. If this is going to get...

Should probably post the example from #163 when complete.

> Another possible example is to implement one of the function-as-a-service protocols with some tuning goodies. @parity3 sweet idea. I'd welcome a PR for something that too 😉 > function-as-a-service...

> You could make it compatible with celery I was gonna say, IMO if you pair `tractor` with `nanomessage` or `zeromq` you can pretty much implement `celery` somewhat trivially, but...

Hmm probably worth linking celery/ceps#27

@parity3 yeah maybe a "micro-service design" tutorial is in order as well. I think we'll end up picking the simplest / hippest of these examples and toss the rest in...

Worth a read is `elixir`'s page on [supervisors](https://elixir-lang.org/getting-started/mix-otp/supervisor-and-application.html) and [dynamic supervisors](https://elixir-lang.org/getting-started/mix-otp/dynamic-supervisor.html).

We had a brief discussion a while back slightly in regard to #190 ([this comment](https://github.com/goodboy/tractor/pull/190)) related apis. For supervisors I actually think we can make quite a nice api by...

[`tenacity`](https://github.com/jd/tenacity#changing-arguments-at-run-time) is an interesting project that seems to be defacto for python restarts. I think the most compatible (though not fully convinced yet) api that we might want to adopt...

A [nice short post](http://catern.com/supervisors.html) from @catern affirming the supervisor at every layer design is the future of process management.