Reactive Applications with Akka.NET

List of Figures

Chapter 1. Why reactive?

Figure 1.1. Reactive systems: responsive, resilient, elastic, message-driven

Figure 1.2. Actors communicate much like people with mobile phones do.

Chapter 2. Reactive application design

Figure 2.1. Creating one actor per shopping cart allows each shopping cart to be accessed independently of the others. This means there’s no contention for resources between User 1 and User 2.

Figure 2.2. The use of state machines with actors in Akka.NET allows you to simplify the process of developing actors with complex internal logic.

Figure 2.3. Creating child actors allows you to perform dangerous work by isolating it from the rest of the application.

Figure 2.4. Sending messages between actors is a fundamental ...