List of Tables

Chapter 3. Understanding Akka

Table 3.1. Message-delivery methods

Chapter 4. Mapping from domain to toolkit

Table 4.1. An actor needs to have behavior, state, and asynchronous messages. Check which candidates have all three features to decide which could be implemented as actors.

Table 4.2. When you have identified the primary actors, begin mapping other parts of the domain to roles in a reactive system.

Table 4.3. Akka routing logic

Table 4.4. Akka dispatchers

Chapter 7. Reactive streaming

Table 7.1. Akka Streams processing stages may be categorized based on the number of inputs and outputs.

Chapter 8. CQRS and Event Sourcing

Table 8.1. Events that have occurred on the employee aggregate

Table 8.2. The read projection of the employee before the termination occurs

Table 8.3. The read projection of the employee after the termination occurs

Chapter 9. A reactive interface

Table 9.1. Comparing Akka HTTP, Lagom, and Play

Chapter 10. Production readiness

Table 10.1. Most providers support the Java API but not a specialized Scala API. Check http://mng.bz/Gvr3 for the latest support information.