Reactive Design Patterns

Summary

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. Foreword by Jonas Bonér.

Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.

About the Technology

Modern web applications serve potentially 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.

About the Book

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’s Inside

• 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

About the Reader

Most examples use Scala, Java, and Akka. Readers should be familiar with distributed systems.

About the Author

Dr. Roland Kuhn led the Akka team at Lightbend and coauthored the Reactive Manifesto. Brian Hanafee and Jamie Allen are experienced distributed systems architects.

Table of Contents

PART 1 – INTRODUCTION
Chapter 1. Why Reactive?
Chapter 2. A walk-through of the Reactive Manifesto
Chapter 3. Tools of the trade

PART 2 – THE PHILOSOPHY IN A NUTSHELL
Chapter 1. Message passing
Chapter 2. Location transparency
Chapter 3. Divide and conquer
Chapter 4. Principled failure handling
Chapter 5. Delimited consistency
Chapter 6. Nondeterminism by need
Chapter 7. Message flow

PART 3 – PATTERNS
Chapter 1. Testing reactive applications
Chapter 2. Fault tolerance and recovery patterns
Chapter 3. Replication patterns
Chapter 4. Resource-management patterns
Chapter 5. Message flow patterns
Chapter 6. Flow control patterns
Chapter 7. State management and persistence patterns

Subscribe