Neil Mitchell introduces the Shake build system. Users of Shake write a Haskell program which makes heavy use of the Shake library, while still allowing the full power of Haskell to be used.
Thomas Kristensen describes the overall architecture of Composer, a system for composing musing, showing how to build a system that achieves responsiveness while still being flexible.
Dustin Getz,Daniel Miladinov demonstrate using Facebook React to build a CRUD editor, highlighting React's application of functional programming and immutability to manage complex application state.
Mark Seemann uses F# to demonstrate how to use functional design with TDD to remove the need for Mock objects.
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.
Simon Marlow explains how to use Haxl to automatically batch and overlap requests for data from multiple data sources.
Dean Wampler takes a look at SQL’s resurgence and specific example technologies, including: NewSQL, Hybrid SQL, SQL abstractions on top of file-based data, SQL as a functional programming language.
Elasticity is a key component in reactive systems and James Ward navigates the different characteristics of different implementations of this concept: Akka, Scala, RxJava, and more.
Rachel Reese sees reactive services and functional languages as a natural pair, demonstrating how functional concepts such as mailboxes and async workflows can help one craft reactive services.
Jonathan Bell & Gail Kaiser introduce Phosphor, a dynamic taint tracking system for the JVM, describing the approach used to achieve portable taint tracking.
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.
Marius Eriksen explains Twitter's experiences with functional programming (with Scala) @ Twitter: where functional techniques worked and where not. Also: how the Scala language has scaled with Twitter