Erlang OTP Case Studies
Analyze real-world examples and best practices from large-scale Erlang OTP deployments, learning from industry successes.
Erlang OTP Case Studies is a free Erlang OTP: Distributed & Fault-Tolerant Systems Programming lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Erlang OTP: Distributed & Fault-Tolerant Systems Programming learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Learning from Erlang's Giants
Why is Erlang chosen for mission-critical systems? Its unique strengths – concurrency, fault tolerance, and distribution – make it ideal for applications needing near-perfect uptime.
Today, we'll explore how major real-world projects leverage these Erlang/OTP features to build highly robust and scalable systems.
Ericsson AXD 301: Telecom Reliability
Ericsson's AXD 301, a massive ATM switch, was one of Erlang's earliest and most famous success stories. It achieved "five nines" (99.999%) availability, meaning less than 5 minutes of downtime per year.
This incredible reliability was largely due to Erlang's:
- Fault Tolerance: Supervisors automatically restarting failed components.
- Hot Code Upgrades: Updating software without service interruption.
- Process Isolation: Failures in one part don't bring down the whole system.
Simulating AXD 301's Resilience
The AXD 301's resilience came from processes that could fail and be restarted by supervisors. This tiny example shows a worker that intentionally crashes, and its supervisor immediately restarts it, demonstrating a core Ericsson principle.
-module(crash_demo).
-behaviour(gen_server).
-export([start_link/0, init/1, handle_call/3, handle_cast/2, handle_info/2, terminate/2, code_change/3]).
-export([crash_me/0, main/0]).
%% Worker functions (behaves as a gen_server)
start_link() -> gen_server:start_link({local, ?MODULE}, ?MODULE, [], []).
init([]) -> io:format("Worker started!~n"), {ok, nil}.
crash_me() -> gen_server:call(?MODULE, crash).
handle_call(crash, _From, State) ->
io:format("Worker intentionally crashing!~n"),
exit(i_crashed), %% Simulate a crash
{reply, ok, State};
handle_call(_Req, _From, State) -> {reply, ok, State}.
handle_cast(_Msg, State) -> {noreply, State}.
handle_info(_Info, State) -> {noreply, State}.
terminate(_Reason, _State) -> io:format("Worker terminating.~n").
code_change(_OldVsn, State, _Extra) -> {ok, State}.
%% Supervisor part (embedded for this demo)
start_supervisor() ->
supervisor:start_link({local, demo_sup}, ?MODULE, supervisor). %% Pass 'supervisor' as InitArgs
%% This init/1 is for the supervisor behavior callback
init(supervisor) ->
SupFlags = #{strategy => one_for_one, intensity => 1, period => 5},
ChildSpecs = [
#{id => my_worker,
start => {?MODULE, start_link, []}, %% Start the worker part of this module
restart => permanent,
shutdown => 5000,
type => worker,
modules => [?MODULE]}
],
{ok, {SupFlags, ChildSpecs}}.
%% Main entry point for runnable
main() ->
io:format("Starting supervisor and worker...~n"),
{ok, _SupPid} = start_supervisor(),
timer:sleep(100), %% Give worker time to start
io:format("Worker PID before crash: ~p~n", [whereis(?MODULE)]),
crash_me(), %% Trigger crash of the worker part
timer:sleep(100), %% Give supervisor time to restart
io:format("Worker PID after restart: ~p~n", [whereis(?MODULE)]),
ok.WhatsApp: Billions of Messages
WhatsApp handled billions of messages daily with a relatively small engineering team, largely thanks to Erlang. Its architecture efficiently managed massive concurrent user connections by leveraging:
- Massive Concurrency: Erlang's lightweight processes (millions per node) allowed handling countless simultaneous users.
- Message Passing: Asynchronous message passing between processes mimicked the real-world communication flow.
- Distribution: Erlang's built-in distribution enabled seamless scaling across multiple server nodes.
WhatsApp's Core: Simple Messaging
At its heart, WhatsApp is about processes sending messages. This snippet shows two processes communicating, illustrating the fundamental building block of their system.
-module(messenger).
-export([start_sender/1, start_receiver/0, main/0]).
%% Receiver process
start_receiver() ->
spawn(fun() -> receiver_loop() end).
receiver_loop() ->
receive
{message, From, Msg} ->
io:format("Receiver (~p) got: ~s from ~p~n", [self(), Msg, From]),
From ! {ack, self()},
receiver_loop();
_ ->
io:format("Receiver got unknown message.~n"),
receiver_loop()
end.
%% Sender process
start_sender(ReceiverPid) ->
spawn(fun() -> sender_loop(ReceiverPid) end).
sender_loop(ReceiverPid) ->
Msg = "Hello from sender!",
io:format("Sender (~p) sending '~s' to ~p~n", [self(), Msg, ReceiverPid]),
ReceiverPid ! {message, self(), Msg},
receive
{ack, _Receiver} ->
io:format("Sender (~p) received acknowledgement.~n", [self()]);
_ ->
io:format("Sender got unexpected reply.~n")
end,
timer:sleep(100),
ok. %% Only send one message for this demo
%% Main entry point for runnable
main() ->
io:format("Starting messaging demo...~n"),
Receiver = start_receiver(),
timer:sleep(50), %% Give receiver a moment to start
Sender = start_sender(Receiver),
io:format("Sender PID: ~p, Receiver PID: ~p~n", [Sender, Receiver]),
timer:sleep(500), %% Allow messages to exchange
ok.RabbitMQ: Reliable Message Queues
RabbitMQ, a widely used open-source message broker, relies heavily on Erlang/OTP for its robustness and scalability. It provides critical features such as:
- Reliability: Persistent message queues ensure messages aren't lost even if the server crashes.
- Clustering: Multiple RabbitMQ nodes can form a cluster, sharing queues and data, thanks to Erlang's distribution.
- Fault Tolerance: Supervisors manage internal components, ensuring continuous operation and automatic recovery.
Best Practice: Embrace 'Crash First'
A key takeaway from these case studies is Erlang's "crash first" philosophy. Instead of trying to prevent every error, systems are designed to crash cleanly and be restarted by a supervisor. This approach leads to:
- Simpler error handling logic.
- More robust systems that automatically recover.
- Easier identification of root causes through crash reports.
Best Practice: Seamless Hot Upgrades
Another powerful feature utilized in high-availability systems like Ericsson's is hot code loading and upgrades. Erlang allows you to replace running code modules without stopping the application or losing its state.
- Essential for systems requiring continuous uptime.
- Minimizes maintenance windows.
- Enables rapid deployment of fixes and new features.
Best Practice: Scale with Distribution
Erlang's built-in support for distributed computing is fundamental to scaling systems like WhatsApp and RabbitMQ. It allows applications to seamlessly span multiple machines or nodes.
- Node Communication: Processes on different machines can communicate as if they were local.
- Global Registration: Register process names globally, making them discoverable across the cluster.
- Fault Tolerance: Distribute workload and ensure that the failure of one node doesn't bring down the entire system.
Check Your Understanding
Based on the real-world case studies discussed, which of the following are key benefits of using Erlang/OTP for building highly available and scalable systems?
Recap: Learning from Success
We've explored how major projects like Ericsson AXD 301, WhatsApp, and RabbitMQ leverage Erlang/OTP's unique strengths.
- Fault tolerance via supervision allows systems to recover automatically from failures.
- Hot code upgrades enable continuous service without downtime, crucial for critical systems.
- Massive concurrency and distribution are key to scaling applications and building resilient architectures.
These principles are central to designing and building robust, real-world Erlang applications.
Frequently asked questions
Is the “Erlang OTP Case Studies” lesson free?
Yes — the full text of “Erlang OTP Case Studies” is free to read here on the web, and the Erlang OTP: Distributed & Fault-Tolerant Systems Programming course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Erlang OTP: Distributed & Fault-Tolerant Systems Programming course, upgrade to CoddyKit PRO.
What will I learn in “Erlang OTP Case Studies”?
Analyze real-world examples and best practices from large-scale Erlang OTP deployments, learning from industry successes. You practise Erlang OTP: Distributed & Fault-Tolerant Systems Programming with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Erlang OTP: Distributed & Fault-Tolerant Systems Programming?
No prior experience is required. Erlang OTP: Distributed & Fault-Tolerant Systems Programming on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Erlang OTP Case Studies” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Erlang OTP: Distributed & Fault-Tolerant Systems Programming lesson?
Yes. Every Erlang OTP: Distributed & Fault-Tolerant Systems Programming lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.