Beyond the buzzword: A reactive web application in practice
summary
Live-coding builds a small Scala Play Framework web app: a websocket front end that creates one lightweight actor per connection, sends queries to the Twitter API via nonblocking Futures, and routes results back; failures go through a Circuit Breaker (configured for 2 failures, 5s timeout, 5s reset) and actor-to-future bridging uses the pipe pattern so exceptions don't fail silently. Demo shows echo and Twitter queries (artificial 1ms timeout to trip the breaker), and load testing uses Gatling and Bees with Machine Guns; deployment options include Clever Cloud.
AI-written summary · about
chapters (10)
- 0:00Introduction to reactive apps
- 7:10Evolution of web architectures
- 14:57Hardware trends and reactive needs
- 15:37Building a reactive web app
- 23:23Live coding the websocket
- 31:48Handling failures with futures
- 39:14Circuit breakers for resilience
- 46:40Deployment strategies
- 51:55Load testing reactive systems
- 57:15Closing remarks
related talks
43mBeyond the buzzword: a reactive web application in practice
52mBeyond the Buzzword: A Reactive Web Application in Practice
52mBuilding Reactive Apps
42mReactive applications with WebSockets
46mIntegration of Distributed Real-time Data Computing in a Web App
47mReactive Spring
38mBest Practices in Reactive Application with Java 1.8 and Play
02h 45mReactive Revolution