Akka Typed
Note
This module is ready to be used in production, but it is still marked as may change. This means that API or semantics can change without warning or deprecation period, but such changes will be collected and be performed in Akka 2.6.0 rather than in 2.5.x patch releases.
- Getting Started Guide
- Introduction to Akka
- Why modern systems need a new programming model
- How the Actor Model Meets the Needs of Modern, Distributed Systems
- Overview of Akka libraries and modules
- Introduction to the Example
- Part 1: Actor Architecture
- Part 2: Creating the First Actor
- Part 3: Working with Device Actors
- Part 4: Working with Device Groups
- Part 5: Querying Device Groups
- Actors
- Dispatchers
- Coexistence
- Actor lifecycle
- Interaction Patterns
- Fault Tolerance
- Actor discovery
- Routers
- Stash
- Streams
- Cluster
- Distributed Data
- Cluster Singleton
- Cluster Sharding
- Persistence
- Dependency
- Introduction
- Example
- Cluster Sharding and persistence
- Accessing the ActorContext
- Changing Behavior
- Effects and Side Effects
- Replies
- Serialization
- Recovery
- Tagging
- Event adapters
- Wrapping Persistent Behaviors
- Journal failures
- Journal rejections
- Stash
- Persistence - coding style
- Persistence - snapshotting
- Behaviors as Finite state machines
- Testing