Reactive Design Patterns

List of Figures

Chapter 1. Why Reactive?

Figure 1.1. The structure of Reactive values

Figure 1.2. Partially decomposed module hierarchy of the hypothetical Gmail implementation

Chapter 2. A walk-through of the Reactive Manifesto

Figure 2.1. The front-end server for images first checks an in-memory cache, then attempts to retrieve the image from storage, and finally returns a fallback image if neither is successful.

Figure 2.2. Using standard listener threads and a connection pool results in the listeners acting as queue entries, with overflow into the system TCP buffers.

Figure 2.3. Adding an explicit queue to manage access to the database connection pool allows you to manage the maximum system latency separately from the listener thread pool ...