There is no resilience without supervision, at every level. Thread, process, node, machine, DC, etc. Erlang figured this out 30+ years ago.
-
-
Replying to @jamie_allen
@jamie_allen What they figured out is that there is no resilience without concurrency. Supervision followed, and finally, hierarchies.1 reply 5 retweets 7 likes -
Replying to @FrancescoC
@FrancescoC now that's a cool concept. Any more words on why concurrency for resilience? /cc@jamie_allen1 reply 0 retweets 0 likes -
Replying to @boulderdanh
@boulderDanH@jamie_allen If a process fails, you need another process to handle the failure.1 reply 0 retweets 1 like -
Replying to @FrancescoC
@FrancescoC is the point that as soon as you move to two processes you've got to reason about concurrent behavior? /cc@jamie_allen1 reply 0 retweets 0 likes -
Replying to @boulderdanh
@boulderDanH@jamie_allen No, the point is that with sequential code, you might catch an exception but could have a corrupt state.2 replies 0 retweets 0 likes
@boulderDanH @jamie_allen Solution is terminating the process. When you do so, you need to tell someone. That is your second process.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.