WHAT I LEARNED ABOUT AKKA STREAMS BY MAKING A GAME WITH IT
summary
Built an arcade game with Akka Streams plus libGDX and JMonkey to test low latency inputs and finds concrete fixes not theory. Exceptions inside stages require a custom decider to log and choose Resume or Stop. Custom actor publisher had an off‑by‑one bug; replacing it with Source.actorRef removes jitter. Never use zero element buffers for user input use minimal buffering and batch or sum tick deltas with expand/extrapolate to avoid stalls. For UI thread work use a sync queue rather than a calling‑thread dispatcher.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:15What this talk isnt about
- 1:55Resources to get started
- 2:43Why game development
- 5:35Add a decider
- 6:26Debug logging
- 7:09Game engines
- 9:11Actor publisher
- 10:41Output
- 10:56Bug
- 11:40SourceAct
- 12:00Comparison
- 12:12Lesson
- 13:52Graph DSL
- 14:51Make your own tool
- 15:55Multiple sources
- 17:05Stage contract
- 19:39Stream structures
- 20:25Ensure flow
- 21:57Thread loss
- 23:21Sync Queue
- 24:07Batch Method
- 24:55Summary
related talks
25mBUILDING MULTIPLAYER GAME BACKEND WITH AKKA ON AWS LAMBDA
47mPICKUP DATA: A Kafka Adventure Game
43mPICKUP DATA - A Kafka Adventure Game
38mAdvanced Game Development Topics
49mCoding video game as a hobby, possible and (kinda) easy with Java!
47mEnterprise Java Can Do Games Too!
18mOvercoming latency, How we build a Cloud Game service with Go
35mBuilding Game Engines in Elixir