Chapter 15. Actor persistence
In this chapter
- Using event sourcing for durability
- Recording and recovering durable state with persistent actors
- Clustering persistent actors
The in-memory state of an actor is lost when an actor is stopped or restarted, or when the actor system crashes or shuts down. This chapter is all about how to make this state durable using the akka-persistence module.
It’s quite common to use a database API for creating, retrieving, updating, and deleting records (also known as CRUD operations). Database records are often used to represent the current state of a system. The database acts as a container for shared mutable state in this case.
It should come as no surprise that Akka persistence prefers a more immutable ...
Get Akka in Action now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
