pekko/akka-docs/rst/scala/index-actors.rst

Actors
======

.. toctree::
   :maxdepth: 2

   actors
   typed-channels
   typed-actors
   fault-tolerance
   dispatchers
   mailboxes
   routing
   fsm
   persistence
   testing
restructure ToC of reST docs - completely decouple Java/Scala and remove heading suffixes - move all images into images/ - move cluster docs into “official” place 2013-04-19 13:21:15 +02:00			`Actors`
			`======`

			`.. toctree::`
			`:maxdepth: 2`

			`actors`
			`typed-channels`
			`typed-actors`
			`fault-tolerance`
			`dispatchers`
Split mailbox documentation into a separate section. See #3341 2013-05-24 15:59:53 +02:00			`mailboxes`
restructure ToC of reST docs - completely decouple Java/Scala and remove heading suffixes - move all images into images/ - move cluster docs into “official” place 2013-04-19 13:21:15 +02:00			`routing`
			`fsm`
akka-persistence prototype The most prominent changes compared to eventsourced are: - No central processor and channel registry any more - Auto-recovery of processors on start and restart (can be disabled) - Recovery of processor networks doesn't require coordination - Explicit channel activation not needed any more - Message sequence numbers generated per processor (no gaps) - Sender references are journaled along with messages - Processors can determine their recovery status - No custom API on extension object, only messages - Journal created by extension from config, not by application - Applications only interact with processors and channels via messages - Internal design prepared for having processor-specific journal actors (for later optimization possibilities) Further additions and changes during review: - Allow processor implementation classes to use inherited stash - Channel support to resolve (potentially invalid) sender references - Logical intead of physical deletion of messages - Pinned dispatcher for LevelDB journal - Processor can handle failures during recovery - Message renamed to Persistent This prototype has the following limitations: - Serialization of persistent messages and their payload via JavaSerializer only (will be configurable later) - The LevelDB journal implementation based on a LevelDB Java port, not the native LevelDB (will be configurable later) The following features will be added later using separate tickets: - Snapshot-based recovery - Reliable channels - Journal plugin API - Optimizations - ... 2013-09-14 14:19:18 +02:00			`persistence`
restructure ToC of reST docs - completely decouple Java/Scala and remove heading suffixes - move all images into images/ - move cluster docs into “official” place 2013-04-19 13:21:15 +02:00			`testing`