Hacker News Reader

I found a functional link to one of the papers, and I figured there’d be some mention of Erlang, but nada. No mentions of actors, either, although that’s less directly relevant.

https://www.usenix.org/legacy/event/osdi04/tech/full_papers/...

Well, a bit more radical than that.

In Erlang world, I think this is basically advocating that your GenServer "handle_call/3" "handle_cast/2" methods should only ever return "{stop,...}" and never "{reply...}" or "{ok...}"

I don’t read it that way; I think they’re advocating architecting a collection of components and rebooting them at the first sign of trouble. So, basically Erlang.

> This cheap form of recovery engenders a new approach to high availability: microreboots can be employed at the slightest hint of failure, prior to node failover in multi-node clusters, even when mistakes in failure detection are likely; failure and recovery can be masked from end users through transparent call-level retries; and systems can be rejuvenated by parts, without ever being shut down.

Alternatively, https://mirage.io/ -- sort of, anyway