Chapter 2. Reactive application design

 

This chapter covers

  • Designing reactive systems with Akka.NET design patterns
  • Exploring application design concepts
  • Reactive design trade-offs

In chapter 1, you saw many reasons why you might want to design an application using the principles laid out in the Reactive Manifesto—reasons primarily driven by the changing face of technology over the past several decades. Whereas computers were once rarities, used primarily by researchers or organizations with sufficient funds, they have since been transformed into the commonplace, with the vast majority of households now having at least one computer, smartphone, or tablet. This number is set to grow with the introduction of the Internet of Things, which is transforming many of the mundane tasks we perform on a daily basis by harnessing the power of an interconnected network of smart devices. This transformation is likely to replicate many of the changes we’ve already seen in industry over the past few decades, as companies adapt to provide their services in the internet age.

2.1. Basic reactive system design

2.2. Reactive e-commerce application with actors

2.3. Building on reactive foundations

Summary

sitemap