Erlang OTP: Distributed & Fault-Tolerant Systems Programming · レッスン

クラッシュファースト設計

障害を前提としSupervisorが処理する自己修復システムを設計する、「クラッシュファースト」の原則を学びます。

「クラッシュファースト設計」はCoddyKit上の無料Erlang OTP: Distributed & Fault-Tolerant Systems Programmingレッスンです。これはレッスン3/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはErlang OTP: Distributed & Fault-Tolerant Systems Programming学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Erlang OTP: Distributed & Fault-Tolerant Systems Programmingコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Embrace the Crash-First Philosophy

In Erlang, we don't just handle errors; we embrace them! This is the "crash-first" principle.

Instead of trying to prevent every possible error with complex checks, Erlang systems are designed to let processes crash when something unexpected happens.

The system then relies on another component, the supervisor, to detect the crash and restart the failed process, ensuring continuous operation.

This approach leads to more robust, self-healing applications.

Defensive vs. Crash-First

Many programming paradigms emphasize "defensive programming":

Extensive input validation.
Complex error codes and handling logic.
Trying to recover *within* the failing function.

Crash-first flips this: If a process encounters an unrecoverable error, it should just crash. Let a higher-level entity (the supervisor) deal with the recovery.

Supervisors Make it Work

The 'crash-first' strategy wouldn't work without supervisors. Supervisors are special Erlang processes designed to monitor other processes (their children).

When a child process crashes, the supervisor detects its termination and acts according to a predefined restart strategy.

This allows the faulty process to be restarted in a known, clean state, without affecting the rest of the system.

Isolation is Key

Erlang's lightweight processes are isolated from each other. This isolation is crucial for crash-first.

If one process crashes, it doesn't directly bring down other processes. Each process has its own memory and execution context.

This means a supervisor can restart a faulty process without fear of corrupting the state of its siblings or the entire application.

A Process That Crashes

Let's see a simple Erlang process that will intentionally crash. We'll use division by zero, a common way to trigger an error.

Notice how start/0 spawns a new process that tries to perform the faulty operation.

When you run this, you'll see an error message, but the Erlang VM itself won't crash.

-module(crashy_process_example).
-export([start/0, crash_me/0]).

crash_me() ->
    io:format("Crashy process ~p starting...~n", [self()]),
    timer:sleep(500), % Give it a moment
    Result = 10 / 0, % This will cause a badarith error
    io:format("This line will not be reached: ~p~n", [Result]).

start() ->
    spawn(fun crash_me/0).

% To run:
% 1. Compile: c(crashy_process_example).
% 2. Start: crashy_process_example:start().

Supervisor Restarts a Crash

Now, let's wrap our crashing logic with a simple supervisor. The supervisor will detect its child's crash and restart it.

We define a child spec for our crashing function (now defined directly within the supervisor module) and use the one_for_one strategy.

Run the code. Observe how the process crashes and is restarted automatically by the supervisor! You'll see "Crashy process X starting..." multiple times.

-module(my_supervisor_example).
-behaviour(supervisor).
-export([start_link/0, init/1, crash_me/0]). % Export crash_me for child_spec

crash_me() ->
    io:format("Crashy process ~p starting...~n", [self()]),
    timer:sleep(1000), % Give it a second
    Result = 10 / 0, % This will cause a badarith error
    io:format("This line will not be reached: ~p~n", [Result]).

start_link() ->
    supervisor:start_link({local, ?MODULE}, ?MODULE, []).

init([]) ->
    % Child spec for our crashing function
    CrashyChild = {crashy_child_id, % Unique ID for the child
                   {?MODULE, crash_me, []}, % {Module, Function, Args}
                   permanent, % Restart if it terminates
                   5000,      % Max restart intensity
                   worker,    % Type of process
                   [?MODULE]}, % List of modules it depends on (used for code loading)
    Children = [CrashyChild],
    % Restart strategy: one_for_one means only the crashing child restarts
    Strategy = {one_for_one, 1, 5}, % Max 1 restart in 5 seconds
    {ok, {Strategy, Children}}.

% To run:
% 1. Compile: c(my_supervisor_example).
% 2. Start: my_supervisor_example:start_link().

Design with Failure in Mind

Embracing crash-first means a shift in how you design your applications.

Identify Failure Domains: Group related processes under supervisors. If one fails, only that group is affected.
Idempotent Operations: Design processes so that restarting them or re-executing an operation doesn't cause negative side effects.
External State: Minimize mutable state held within a process that would be lost on a crash. Use persistent storage (like ETS or Mnesia) for critical data.

Managing State in Crash-First

When a process crashes and restarts, its internal state is lost. This is by design, providing a clean slate.

For processes that manage important state, you need a strategy:

Initialize from Source: On restart, fetch the necessary state from a reliable source (database, configuration file, another persistent process).
Externalize State: Store critical, shared state in ETS tables, Mnesia, or a database, rather than solely within a process's heap.

This ensures that even after a crash, the process can resume its duties with correct information.

Why Crash-First is Powerful

Adopting the crash-first principle offers significant advantages:

Increased Reliability: Systems automatically recover from transient errors.
Simpler Code: Less need for complex, defensive error-handling logic within each function.
Fault Tolerance: The application continues to operate even if parts fail.
Easier Debugging: Crashes clearly indicate unexpected states, rather than masking issues with complex recovery attempts.

Quick Check: Crash-First

Which statements accurately describe the "crash-first" principle in Erlang and its benefits?

Recap: Designing for Crash-First

We've explored the powerful "crash-first" philosophy in Erlang:

It's about letting processes crash on unrecoverable errors.
Supervisors are key, monitoring and restarting crashed processes.
Erlang's process isolation ensures local crashes don't bring down the whole system.
Designing for crash-first involves thinking about failure domains, idempotent operations, and externalizing critical state.

This approach simplifies code, increases reliability, and builds truly fault-tolerant systems.

よくある質問

「クラッシュファースト設計」レッスンは無料ですか？

はい。「クラッシュファースト設計」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Erlang OTP: Distributed & Fault-Tolerant Systems Programmingコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Erlang OTP: Distributed & Fault-Tolerant Systems Programmingコースには全4レッスンが含まれています。

「クラッシュファースト設計」で何を学びますか？

障害を前提としSupervisorが処理する自己修復システムを設計する、「クラッシュファースト」の原則を学びます。ブラウザで直接実行するハンズオンコードでErlang OTP: Distributed & Fault-Tolerant Systems Programmingを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Erlang OTP: Distributed & Fault-Tolerant Systems Programmingを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのErlang OTP: Distributed & Fault-Tolerant Systems Programmingは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン3/4です。

「クラッシュファースト設計」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このErlang OTP: Distributed & Fault-Tolerant Systems Programmingレッスンでコードを書いて実行できますか？

はい。すべてのErlang OTP: Distributed & Fault-Tolerant Systems Programmingレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Erlang OTP: Distributed & Fault-Tolerant Systems Programmingに戻る