Joe Armstrong outlines the architectural principles needed for building scalable fault-tolerant systems built from small isolated parallel components which communicate though well-defined protocols.
David Craelius tells the story of Klarna building an online payment system in Erlang and their approach to solving the nightmare of technical debt accumulated during a period of fast expansion.
Torben Hoffmann looks at the status of Erlang using the technology life cycle lenses of Geofrey More and in particular discuss if Erlang is before, in or after the Chasm.
Steve Vinoski overviews Yaws with code samples to highlight some of its features. Steve also discusses internals of Yaws, and how powerful Erlang can be for web development and distributed systems.
José Valim introduces Elixir, a programming language for the Erlang VM – an attempt to provide better abstractions and productivity tools like protocols and macros usually required for web development
Garrett Smith discusses building reliable systems starting with lessons from Erlang, then outlining a set of principles and the practices for applying them in languages such as Ruby, Python, and Java.
Jesse Newland discusses how GitHub pages were re-written with Erlang, Riak and Webmachine in order to improve their performance.
Fred Hebert discusses using Erlang for a real-time bidding system, providing some details of its design and architecture, along with lessons learned while implementing it.
Mike Williams discusses large vs. small software development teams, concluding that smaller teams are better suited for most cases.
Richard Carlsson introduces and demoes a library for using template strings with meta-variables. The library was used at Klarna to implement a DSL for business logic.
Erik Happi Stenman discusses 4 scalability basic requirements: the right business model, the right technology, the right people, and the right (amount of) process.
Andy Gross reports on how Basho used Riak and Erlang to build their cloud storage service.