Joseph Blomstedt presents ongoing work to build a new set of high performance data structures for Erlang, including both single process data structures as well as various concurrent data structures.
Ransom Richardson presents the Talko service architecture, its implementation and operation in the cloud, why they are using Erlang for it and key things learned along the way.
Garrett Smith outlines a methodology for pattern discovery and presents a number of specific patterns that Erlang programmers can use to build programs that feel alive.
Simon Thompson shows how Wrangler can help with making systems run on multi-core hardware, including three Wrangler refactoring techniques for retrofitting concurrency to Erlang applications.
Daniel Pezely discusses the 10 fold performance increase of a Lisp and C system after rewriting it in Erlang, outlining where issues existed before and the design and implementation of the new system.
Christopher Meiklejohn looks at applying two techniques together, deterministic data flow programming and conflict-free replicated data types, to create highly available and fault-tolerant systems.
Torben Hoffmann talks about how to design systems with asynchronous message passing between processes that do not share any memory.
Francesco Cesarini illustrates how the Erlang way of thinking about problems leads to scalable and fault-tolerant designs, describing 3 ways of clustering Erlang nodes within the server side domain.
Dan Macklin explains why bet365 has adopted Erlang as a core development platform and goes through the highs and lows of managing change in one of the world's biggest on-line bookmakers.
Brian Troutwine examines how functional programming and other concepts championed by Erlang can yield reactive services with just a change in thinking and a different approach to design.
Ryan Cromwell introduces Elixir, a , functional distributed meta programming language inspired by Ruby and compiling to Erlang VM, covering pattern matching, pipelines and tail-call recursion.
Torben Hoffmann shares a number of patterns from Erlang systems, modeled through Object-Process Methodology, discussing their impact on business needs.