Torben Hoffmann shares a number of patterns from Erlang systems, modeled through Object-Process Methodology, discussing their impact on business needs.
Rick Reed shares scalability and reliability insights, techniques, and hacks used and learned developing WhatsApp on an Erlang/FreeBSD infrastructure.
Jane Street runs a large trading business on software written almost entirely in OCaml, a statically typed functional language. Yaron Minsky shows the reasons for choosing Ocaml and how it worked out.
Kresten Krab Thorup introduces Erjang, an Erlang VM based on the JVM, disclosing some of its internal workings and challenges building it.
Richard Minerich explains how ideas and tools from functional programming can save time, prevent subtle mistakes in data science, and how he incorporates them into his everyday workflow.
Fred Hebert introduces two strategies for handling overload -load-shedding and back-pressure- along with different ways to make them work in Erlang focusing on the importance of planning for overload.
Benoît Chesneau discusses creating, scaling and reusing HTTP connections, summarizing techniques used to reduce memory usage in Erlang and ways to handle massive client connections efficiently.
Brian Troutwine shares insight on using Erlang for a highly concurrent and very low latency bidding system implemented by Adroll.
Alissa Pajer discusses through examples how to understand and write cleaner and more maintainable functional code using the Category Theory.
Glen Peterson uses the Expression Problem to compare refactoring in Java, Scala and Clojure, showing how traits minimize changes in Scala when an interface changes and how Clojure avoids some of the issues.
Sponsored by Goldman Sachs. Java 8 has Streams, Scala has parallel collections, and GS Collections has ParallelIterables. Since we use parallelism to achieve better performance, it's interesting to ask: how well do they perform? We'll look at how these three APIs work with a critical eye toward performance. We'll also look at common performance pitfalls.
Bodil Stokke demos building a complete video game from nothing in the span of a conference talk using functional reactive programming.