Using Actors for the Internet of (Lego) Trains
summary
Raspberry Pi–powered Lego trains use camera, RFID, infrared transmitter, speaker and Particle Photon LEDs tied into a Scala/Java backend with AngularJS front end; control runs as actors via Akka remote actors or over Akka HTTP. Benchmarks show remote actors give lower mean and 99th‑percentile latency and a student test estimates 3,300 vs 600 users capacity versus REST; Spring Boot sometimes has lower mean latency but remote actors stay more stable under high load. A working demo includes automated location‑based sequences; practical issues include flaky Wi‑Fi and Raspberry Pi A+ burned units and memory limits.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:48COMPARISON
- 15:38AKKA REMOTE ACTOR CALL
- 16:19AKKA REMOTE ACTOR CONFIGURATION
- 17:53CONCRETE EXAMPLE
- 18:14Server application
- 18:29EXAMPLE MESSAGE
- 26:27ADVANTAGES REMOTE ACTORS
- 26:50ADVANTAGES HTTP
- 28:35GATLING
- 29:32PERFORMANCE TEST SETUP
- 31:00GRADUATION STUDENT
- 37:08CONCLUSION
related talks
25mArchitecting Web Apps - Lights, Camera, Action!
33mLet’s Build K.I.T.T. with JavaScript
43mLet’s build K.I.T.T. with JavaScript
43mLet’s build K.I.T.T. with JavaScript
31mInternet of Things: Connecting Rails with the Real World
32mAdopting Actors... an epic tale of loss and learning
57mBeyond the buzzword: A reactive web application in practice
30mLet’s build K.I.T.T. with JavaScript