Part 2. Building a reactive application

This rest of the book shows you what we believe are the most important things to know about writing reactive applications.

Domain-driven design is particularly useful for reactive applications. Chapter 4 illustrates this design by mapping a domain onto an actor model, including translating some features onto behavior of the toolkit rather than things you have to write yourself. Chapter 5 solidifies your understanding by formalizing key concepts and useful patterns. In chapter 6, we turn to a more concrete programming example, using remote actors to demonstrate how working with asynchronous peers is different from traditional service call-and-response. In chapter 7, you learn about streams and the role of backpressure, and examine the Reactive Streams API for interoperability among different reactive implementations. Chapter 8 addresses the difficult topic of working with persistent data and the different roles of commands and events in your design. Chapter 9 covers alternatives for exposing your reactive services so that they can be consumed by external clients. Finally, chapter 10 puts you on the path to production readiness with brief discussions of testing patterns, application security, logging, tracing, monitoring, configuration, and packaging.