Having Fun with Play! 2, Akka and Websocket
summary
Built Blackbeard CMS to push New York Times content to third parties using Play! 2, Akka and WebSockets; it supports single‑page editing with 5–10 editors per article and handles about 300–400 articles/day. Architecture uses a singleton master + leaf actors pattern with a broadcaster actor and shared enumerators to multicast updates; controllers use Play filter and JSON validation and keep heavy work out of actors. Team of three ships MVP in three months, users adopt it, but a blocking future took system down once and tab refresh causes a brief leaf restart.
AI-written summary · about
chapters (10)
- 0:00Introduction to Blackbeard
- 1:08Challenges and Technologies
- 2:29System Architecture
- 4:42User Management and Data Flow
- 6:09Actor Lifecycle and Glitches
- 7:39Development and Results
- 9:21Lessons Learned: Play API
- 10:32Scala and JSON Best Practices
- 12:12Command System and Validation
- 13:28Asynchronous Programming Tips
related talks
50mDelicious Play recipes for real world
52mBeyond the Buzzword: A Reactive Web Application in Practice
57mBeyond the buzzword: A reactive web application in practice
43mBeyond the buzzword: a reactive web application in practice
46mIntegration of Distributed Real-time Data Computing in a Web App
01h 32mFrom Spring + Java to Spring + Akka - A Journey of Discovery
33mFun With Websockets
42mReactive applications with WebSockets