InfoQ Homepage Reliability Content on InfoQ
-
Let It Crash ... Except When You Shouldn't
Steve Vinoski explains how to avoid some of the Erlang errors that can bring down a system starting from the premise that not all the crashes are welcome as the “Let It Crash” philosophy might suggest
/presentations/Let-It-Crash/en/smallimage/Steve.JPG)
-
Building Reliable Systems from Unreliable Components
Arnon Rotem-Gal-Oz discusses creating a SOA implementation that maintains a good overall reliability in spite of using smaller and a larger number of components.
/presentations/Building-Reliable-Systems/en/smallimage/Rotem.JPG)
-
Rapid and Reliable Releases
Rolf Russell & Andy Duncan discuss rapid and reliable releases from the build/release/devops perspective, considering relationships, metrics, required skills, and the need to cut waste and bottlenecks
/presentations/Rapid-Reliable-Releases/en/smallimage/QTB.png)
-
Message Passing Concurrency in Erlang
Joe Armstrong explains through Erlang examples that message passage concurrency represents the foundation of scalable fault-tolerant systems.
/presentations/Message-Passing-Concurrency/en/smallimage/JoeArmstrong.png)
-
RPC and its Offspring: Convenient, Yet Fundamentally Flawed
Steve Vinoski covers the history of RPC, standardization, distributed objects, CORBA, DCOM, Java, SOAP, WS-*, flaws in RPC, REST vs RPC philosophy, Erlang reliability and concurrency.
/presentations/vinoski-rpc-convenient-but-flawed/en/smallimage/SteveVinoski.jpg)
-
Systems that Never Stop (and Erlang)
Joe Armstrong on 6 reliability laws, Isolation, Concurrency, Failure Detection, Fault Identification, Live Code Upgrade, Stable Storage, showing how they are respected in Erlang, plus some examples.
/presentations/Systems-that-Never-Stop-Joe-Armstrong/en/smallimage/JoeArmstrong.jpg)