Network I/O for a More Civilized Age: The New Akka I/O
summary
Compares Netty/NIO pain with a concrete alternative: Akka I/O uses immutable ByteString for wire data, a pipeline stage model that composes decoding SSL and staging, and a built-in back pressure handler wired to actor stash. Demonstrates a TCP time client/server, shows how commands/events and pipeline handlers translate to domain messages, and suggests futures/promises or reactive streams for client APIs. Claims 90% of async web users still run blocking DB drivers and shows how Akka I/O avoids that by keeping threads small and selectors central so the demo actually runs end to end.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:52The New Akka IO
- 3:18Why Akka IO
- 4:00Nonblocking IO
- 6:07NIO
- 7:10Apache Nina
- 8:11bytebuffer
- 9:56bytestring
- 11:26time protocol
- 13:17byte string
- 14:03IO actors
- 14:59IO facade
- 15:17TCP manager
- 15:28Akka behavior
- 16:00Akka receive loop
- 16:45Akka connected behavior
- 18:01Complex is better
- 19:17Setting up a pipeline
- 19:52Creating a pipeline handler
- 20:27Registering the pipeline
- 22:49Adding SSL support
- 23:42Network Back Pressure
- 24:45Stash
- 25:40Back Pressure
- 26:35Concluding Thoughts
- 28:30Reactive Streams
- 32:39Disk IO
related talks
59mDrinking a river of IoT data with Akka.NET
39mAkka js: Drop Your Actos Outside the JVM Boundaries
01h 31mReactive Streams / Akka Streams
43mGetting real(time) with Akka.NET, React and Redux
56mReal-Time, Distributed Applications w/ Akka.NET, Kubernetes, .NET Core, and Azure Kubernetes Service
39mAsynchronous and Non-Blocking IO with JRuby
49mNode JS
28mThe good, the bad and the ugly of nodejs streams