[macintux]

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.