Reactive Design Patterns
- 7h 23m
- Brian Hanafee, Jamie Allen, Roland Kuhn
- Manning Publications
- 2017
Reactive Design Patterns is a clearly written guide for building message-driven distributed systems that are resilient, responsive, and elastic. In this book you'll find patterns for messaging, flow control, resource management, and concurrency, along with practical issues like test-friendly designs. All patterns include concrete examples using Scala and Akka.
Modern web applications potentially serve a vast numbers of users - and they need to keep working as servers fail and new ones come Online, users overwhelm limited resources, and information is distributed globally. A Reactive application adjusts to partial failures and varying loads, remaining responsive in an ever-changing distributed environment. The secret is message-driven architecture - and design patterns to organize it.
Reactive Design Patterns presents the principles, patterns, and best practices of Reactive application design. You'll learn how to keep one slow component from bogging down others with the Circuit Breaker pattern, how to shepherd a many-staged transaction to completion with the Saga pattern, how to divide datasets by Sharding, and more. You'll even see how to keep your source code readable and the system testable despite many potential interactions and points of failure.
What you'll learn from this book:
- The definitive guide to the Reactive Manifesto
- Patterns for flow control, delimited consistency, fault tolerance, and much more
- Hard-won lessons about what doesn't work
- Architectures that scale under tremendous load
Most examples use Scala, Java, and Akka. Readers should be familiar with distributed systems.
About the Authors
Dr. Roland Kuhn led the Akka team at Lightbend and co-authored the Reactive Manifesto. Brian Hanafee and Jamie Allen are experienced distributed systems architects.
In this Book
-
Foreword
-
About This Book
-
Why Reactive?
-
A Walk-Through of the Reactive Manifesto
-
Tools of the Trade
-
Message Passing
-
Location Transparency
-
Divide and Conquer
-
Principled Failure Handling
-
Delimited Consistency
-
Nondeterminism by Need
-
Message Flow
-
Testing Reactive Applications
-
Fault Tolerance and Recovery Patterns
-
Replication Patterns
-
Resource-Management Patterns
-
Message Flow Patterns
-
Flow Control Patterns
-
State Management and Persistence Patterns
