Please log in to watch this conference skillscast.
What does it means for our programs to be asynchronous and back pressured and why is it so important for scalable services?
During this talk, you will explore the following:
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
Time permitting, you will also discover a demo on a networked application sending back pressure through the application layer, through TCP and into the client application.
YOU MAY ALSO LIKE:
- The JVM and Docker (SkillsCast recorded in June 2016)
- Lightbend Akka for Scala - Professional (in London on 11th - 12th November 2019)
- Functional Concurrency in .NET with C# and F# (in London on 9th - 10th December 2019)
- Scala eXchange London 2019 (in London on 12th - 13th December 2019)
- Scalax2gether Community Day 2019 (in London on 14th December 2019)
- Code Kata: Yilin Wei - Optics with Monocle (in London on 22nd October 2019)
- Don’t keep it to yourself - openness and honesty in the workplace (in London on 30th October 2019)
- Abstract Data Types In The Region Of Abysmal Pain, And How To Navigate Them (SkillsCast recorded in September 2019)
- Demystifying Micro-Frontends (SkillsCast recorded in September 2019)
Building Scalable, Back Pressured Services with Akka
Christopher is a Senior Engineer at Lightbend. He is currently on the core Akka team responsible for developing Akka (https://akka.io/), Akka Http, Akka Streams, Reactive Kafka and Alpakka (https://github.com/akka/alpakka). He has previously built trading systems, online television platforms and worked extensively with Apache Cassandra. Likes: Scala, Java, the JVM, Akka, distributed databases, XP, TDD, Pairing. Dislikes: Untested software and code ownership.