Alexander Daniel Barnabas Kralik Bernhard Huemer Christian Papauschek David Juhasz David Pichsenmeister Dominik Gruber Felix Amerbauer Floor Drees Gerald Löffler Gerhard Hipfinger Lutz Hühnken Manuel Bernhardt Manuel Bernhart Martin Lorenz Mathias Doenitz Michal Bigos Oleg Rudenko Peter Brachwitz Peter Kofler Radim Pavlicek Sebastian Nozzi Stefan Asseg Wolfgang Wagner Yago Alonso
Rea implicit Akka Akka Cluster Akka HTTP Akka Persistence Akka Streams Android BDD BitTorrent Book Review CQRS CSP Communicating Sequential Processes Community Concurrency ConductR Cucumber Dependency Injection Design pattern Devoxx Domain-Driven Design Elasticsearch Event Sourcing Finagle Finatra Functional Programming Gatling Iago JDBC JMX JScala JVM Java JavaScript Kafka Kibana Language Load Testing Logstash Metrics MongoDB Monitoring Netty Node.js Ostrich P2P Parser Combinator Play Framework REST Reactive Streams ReactiveMongo Scala Scala.js ScalaTest Scalaz Selenium Slick Software Architecture Twitter Zipkin conference page object page object pattern pingconf spray ui testing web testing
2015-06-22 2015-05-20 2015-04-15 2015-03-16 2015-02-18 2015-01-13 2014-11-26 2014-10-28 2014-09-30 2014-08-27 2014-07-31 2014-06-25 2014-02-20 2014-01-22 2013-12-17 2013-11-20 2013-09-26 2013-08-26 2013-07-23 2013-06-20 2013-05-22 2013-04-16 2013-03-21
Back to all talks

Reactive Streams & Akka HTTP

Mathias Doenitz
Twitter @sirthias
Homepage http://decodified.com

If you want to provide or consume HTTP-based APIs with Scala (or Java) then this talk is for you: Akka HTTP takes reactive high-performance web interactions to the next level. Fully asynchronous and non-blocking, a type-safe and very powerful declarative API, an immutable HTTP model without compromises, all these are perfectly fitted to the Actor world.

Among many smaller improvements over its predecessor library spray.io, akka-http comes with one major advantage: it is based on a new abstraction called "Reactive Streams” which provides a number of important benefits, not only for working with HTTP.

In this session we’ll first take a closer look into the reactive streams effort, the problems it solves and what programming with reactive streams looks like.

After a short break we’ll then turn to akka-http, how it is used, what improvements it brings over spray and why you will not want to use anything else after having tried it. And of course I'll share the latest roadmap up until making akka-http the new "driver" layer for the Play framework.

Back to all talks