Born from Telecom, Built for Forever
Back in the mid-1980s, the Swedish telecommunications giant Ericsson faced a monumental challenge: how to build phone switches that could handle immense numbers of concurrent calls and, crucially, never, ever fail. A phone network that goes down isn't
just an inconvenience; it's a critical infrastructure failure. The software needed to be absurdly reliable, scalable, and capable of being updated without shutting everything down. When existing languages didn't cut it, a team led by Joe Armstrong, Robert Virding, and Mike Williams created their own. They named it Erlang. Its design philosophy was dictated by the extreme demands of telephony, which accidentally made it perfect for the future internet. It was built for systems that required soft real-time responsiveness and what's known as 'five nines' availability—99.999% uptime.
The Magic: Concurrency and 'Let it Crash'
Erlang's genius lies in two core concepts that were radical for their time. First is its approach to concurrency. Instead of using heavy operating system threads, Erlang uses incredibly lightweight 'processes'. These aren't like the processes in your computer’s task manager; they are tiny, isolated virtual machines that can be created in microseconds and exist by the millions on a single server. They share no memory and communicate only by sending messages to each other, a concept known as the Actor Model. This avoids a whole class of bugs that plague other concurrent systems. Second is its famous 'let it crash' philosophy. Instead of defensively coding to prevent every possible error, Erlang is designed to embrace failure. Processes are monitored by 'supervisors'. If a process fails, its supervisor instantly restarts it in a clean state, often before anyone notices. This creates self-healing systems that are remarkably fault-tolerant.
The Billion-User Chat App and Other Giants
So, where is this battle-tested language hiding? The most famous example is WhatsApp. To handle billions of messages from hundreds of millions of users simultaneously, its small engineering team turned to Erlang. Its ability to manage millions of lightweight, concurrent connections was a perfect match for a chat application. But it's far from the only one. The core infrastructure of companies like Ericsson and Cisco relies heavily on Erlang, meaning a huge portion of the world's internet and mobile traffic flows through Erlang-controlled systems. In the world of finance, companies like Goldman Sachs and Vocalink (a Mastercard company) use it for high-frequency trading platforms and instant payment switches where latency and reliability are paramount. Even the gaming industry uses it; the chat systems for massively popular games like League of Legends and the online services for the Nintendo Switch have used Erlang to connect millions of players at once.
If It's So Great, Why Isn't It Everywhere?
Despite its power, Erlang has never topped the charts as the most popular programming language. Several factors contribute to its niche status. For one, its syntax is unconventional, descending from Prolog rather than the C-family of languages (like Java, C++, and JavaScript) that most developers learn. This can create a steep learning curve. Furthermore, Erlang is a specialist. It’s designed to solve very specific, hard problems related to concurrency and reliability at a massive scale. For many standard business applications, a general-purpose language like Python or Java is often 'good enough' and has a much larger ecosystem of libraries and available developers. Finally, for years it was a proprietary Ericsson technology before being open-sourced in 1998, giving other languages a significant head start in building community and mindshare.
