Building responsive, scalable systems with asynchrony and flow control

Conference

Java Language

Room 1

Friday from 2:30 PM til 3:20 PM

What are reliable ways of building responsive and scalable services? What does it means for our programs to be asynchronous and back pressured and why is it important? This talks aims to answer these questions. We’ll cover:

Thread per request vs asynchronous services
What back pressure is and how to do it all the way down to the network layer
How to achieve all of this with Akka HTTP and Akka Streams
How it compares to other tools for asynchronous programming e.g. CompletableFutures, Observables
Reactive streams specification and API

Time permitting we’ll also demo a networked application built with Akka sending back pressure through the application layer, through TCP and into the client application.

Reactive Streams Akka flow control

Christopher Batey
Christopher (@chbatey) is a Senior Engineer at Lightbend. He works primarily in Scala but also spent 10 years writing Java and a couple of years writing Go. Currently he works on the core Akka team responsible for developing core Akka, Akka Http and Akka Streams. He has previously built trading systems, online television platforms and worked extensively with Apache Cassandra. You can check out his blog at: http://www.batey.info

Christopher Batey

Christopher (@chbatey) is a Senior Engineer at Lightbend. He works primarily in Scala but also spent 10 years writing Java and a couple of years writing Go.

Currently he works on the core Akka team responsible for developing core Akka, Akka Http and Akka Streams. He has previously built trading systems, online television platforms and worked extensively with Apache Cassandra. You can check out his blog at: http://www.batey.info