Best Practices in Reactive Application with Java 1.8 and Play
summary
Live demo builds a chatroom and a REST API using Java 1.8, Play Framework and Akka Streams, showing hot-reload and that the code actually runs. Blocking JPA/JDBC calls are isolated on a separate thread pool via CompletionStage and supplyAsync with an explicit CompletionStage with execution context, using a fixed connection pool sized by CPU count and Hikari: Hikari connection pool. Adds non‑blocking timeouts and a circuit breaker; claims like 80% server reduction at HootSuite and LinkedIn adoption are cited as practical outcomes.
AI-written summary · about
chapters (9)
- 0:00Introduction to Play
- 2:05Live application demo
- 5:00The power of reactive
- 8:37Blocking vs non-blocking
- 10:24Building a basic REST API
- 14:07Integrating databases
- 18:56Performance configuration
- 25:00Handling failures
- 30:17Advanced features and Q&A
