Building Reactive Apps
summary
Reactive apps use async non‑blocking I/O end to end: demo builds a Play (Java 8) app with Typesafe Activator, uses Play + Netty for Java NIO, returns Promise/Future results, delays with a single timer thread, and composes parallel WS calls (james.com + twitter.com) with map/flatMap so threads free up while waiting. Actor example uses Akka actors (actorRef, ask, patterns.pipe, routers like scatter‑gather‑first‑complete) to manage mutable state and retries. Mentions JVM 1MB thread stacks, aiming for threads ≈ CPU cores, millions of actors, and Reactive Streams for nonblocking backpressure.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:44What is Reactive
- 2:30Reactive Web
- 5:27Async Nonblocking
- 8:20Typesafe Activator
- 10:11Play
- 15:53Delayed timeout
- 19:54Promises
- 21:12Web Service Call
- 32:00WS API
- 34:29Demo
- 40:40Code
- 47:21Routers
- 47:46Reactive Streams
- 49:51Questions
related talks
01h 21mReactive Web Applications
38mBest Practices in Reactive Application with Java 1.8 and Play
48mReactive for the Impatient
57mBeyond the buzzword: A reactive web application in practice
47mReactive Spring
41mThe definite guide to reactive programming in Java
52mBeyond the Buzzword: A Reactive Web Application in Practice
24mBringing Reactive Programming to Java and Microservices
