Chapter 17. State management and persistence patterns

The previous chapter introduced the concepts of message rate, load, and time; previously, we had only considered the timeless relationship between different components. This chapter adds another orthogonal dimension to complete the picture: it is the purpose of almost all components to maintain state, and we have not yet discussed how this should be done. The patterns presented are closely related to each other and form a cohesive unit:

  • The Domain Object pattern decouples business logic from communication machinery.
  • The Sharding pattern allows you to store any number of domain objects on an elastic cluster.
  • The Event-Sourcing pattern unifies change notifications and persistence by declaring ...

Get Reactive Design Patterns now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.