Netflix leverages reactive system concepts to produce highly interactive and engaging User Interfaces. By using functional programming, Rx, and an intentional training method, they are able to ramp up their developers to produce reactive code quickly and with few bugs. Jafar explains how Netflix established this practice and gives a few pointers as to how your company can start its own.
Darach Ennis explains the lessons learned from the Complex Event Processing community, reactive programming, the challenges of messaging on mobile platforms, OOP vs Functional and much more.
Ben Christensen explains how Netflix manages to stay online even with millions of users, the Hystrix fault tolerance library, how Netflix discovered reactive programming and why it ported Rx to Java.
Tomas Petricek explains F# and some of its features like Type Providers, pits F# Computation Expressions vs Monads, and highlights issues teaching functional programming to developers, and much more.
Erik Meijer explains the various aspects needed to categorise data stores, how reactive programming fits in with databases, the return to data transformation, denotational semantics, and much more.