List of Figures

 

Chapter 1. What is a reactive application?

Figure 1.1. Shopping cart modeled in typical monolithic architecture style

Figure 1.2. Gunther’s and Amdahl’s laws (http://cmg.org/publications/measureit/2007)

Figure 1.3. The CAP Theorem Venn diagram

Figure 1.4. Shopping cart modeled in reactive architecture style

Figure 1.5. Traits of the Reactive Manifesto (www.reactivemanifesto.org/images/reactive-traits.svg)

Figure 1.6. CRUD shopping cart current state after create

Figure 1.7. CRUD shopping cart current state after customer deletes an item

Figure 1.8. Bank account register transaction log with five transactions

Figure 1.9. A reactive shopping cart stores events.

Figure 1.10. A CRUD shopping cart creates current state; a reactive shopping cart persists behavior.

Figure 1.11. A reactive shopping cart appends a delete event.

Figure 1.12. A CRUD shopping cart deletes overwrites of state; a reactive shopping cart appends a delete event.

Figure 1.13. Logical view of IoT

Chapter 2. Getting started with Akka

Figure 2.1. The illusion of a synchronous call can be the source of unexpected behavior.

Figure 2.2. The sender obtains a reference to address messages to the actor through the actor system.

Figure 2.3. The tourist actor sends inquiry messages to the guidebook. The guidebook actor responds with guidance messages returned to the tourist actor.

Figure 2.4. The layout of the sbt project follows the pattern used by other build systems, such as Maven and Gradle.