The best is yet to come - State of Akka in 2017
summary
Overview of Akka 2.5 and near-future work with concrete outcomes and tools rather than promises: Akka already ships Akka Streams and Akka HTTP with HTTP/2 support, the Play backend migration to the typed HTTP model, Alpakka connectors, stable Persistence Query and Distributed Data CRDTs with delta gossip, and a new remoting codenamed Artery that moves to UDP with lane-based big message handling and claims ~10x throughput improvements; Akka Typed appears as the planned API direction with Java DSL and migration paths.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:56The underlying motto
- 1:41The past
- 2:25Actors
- 13:35Clusters
- 17:02HTTP
- 21:18Persistence
- 24:10Conflictfree data types
- 28:35Streams
- 30:17SPI
- 31:13Flow control
- 31:58Permit systems
- 34:56HTTP to API
- 39:48The typed API
- 45:16Remoting
related talks
41mAkka in Production: Our Story
56mAkka + F# = Akkling
55mExperience report on using Akka in production: pitfalls and rewards
56mAkka in Heterogenous Environments
44mAkka post-mortem in a microservice architecture
44mThe Road to Akka Cluster, and Beyond
41mA tale of futures, actors & pipes: using Akka for large data migration
56mReal-Time, Distributed Applications w/ Akka.NET, Kubernetes, .NET Core, and Azure Kubernetes Service
