Jamie Allen – författare

Avoid common mistakes when building distributed, asynchronous, high-performance software with the Akka toolkit and runtime. With this concise guide, author Jamie Allen provides a collection of best practices based on several years of using the actor model. The book also includes examples of actor application types and two primary patterns of actor usage, the Extra Pattern and Cameo Pattern.

Allen, the Director of Consulting for Typesafe—creator of Akka and the Scala programming language—examines actors with a banking-service use case throughout the book, using examples shown in Akka and Scala. If you have any experience with Akka, this guide is essential.

Delve into domain-driven and work-distribution actor applicationsUnderstand why it’s important to have actors do only one jobAvoid thread blocking by allowing logic to be delegated to a FutureModel interactions as simply as possible to avoid premature optimizationCreate well-defined interactions, and know exactly what failures can occurLearn why you should never treat actors as you would an ordinary classKeep track of what goes on in production by monitoring everythingTune Akka applications with the Typesafe Console

Avoid common mistakes when building distributed, asynchronous, high-performance software with the Akka toolkit and runtime. With this concise guide, author Jamie Allen provides a collection of best practices based on several years of using the actor model. The book also includes examples of actor application types and two primary patterns of actor usage, the Extra Pattern and Cameo Pattern.

Allen, the Director of Consulting for Typesafe—creator of Akka and the Scala programming language—examines actors with a banking-service use case throughout the book, using examples shown in Akka and Scala. If you have any experience with Akka, this guide is essential.

Delve into domain-driven and work-distribution actor applicationsUnderstand why it’s important to have actors do only one jobAvoid thread blocking by allowing logic to be delegated to a FutureModel interactions as simply as possible to avoid premature optimizationCreate well-defined interactions, and know exactly what failures can occurLearn why you should never treat actors as you would an ordinary classKeep track of what goes on in production by monitoring everythingTune Akka applications with the Typesafe Console

Avoid common mistakes when building distributed, asynchronous, high-performance software with the Akka toolkit and runtime. With this concise guide, author Jamie Allen provides a collection of best practices based on several years of using the actor model. The book also includes examples of actor application types and two primary patterns of actor usage, the Extra Pattern and Cameo Pattern. Allen, the Director of Consulting for Typesafe - creator of Akka and the Scala programming language - examines actors with a banking-service use case throughout the book, using examples shown in Akka and Scala. If you have any experience with Akka, this guide is essential.Delve into domain-driven and work-distribution actor applications Understand why it's important to have actors do only one job Avoid thread blocking by allowing logic to be delegated to a Future Model interactions as simply as possible to avoid premature optimization Create well-defined interactions, and know exactly what failures can occur Learn why you should never treat actors as you would an ordinary class Keep track of what goes on in production by monitoring everything Tune Akka applications with the Typesafe Console

 

 

　

 

DESCRIPTION

 

Modern distributed applications must deliver near-realtime performance while simultaneously managing big data and high user loads spread across environments ranging from cloud systems to mobile devices. Unlike traditional enterprise applications which focus on decoupling their internal components by defining programming interfaces, reactive applications go one step further and decouple their components also at runtime. This makes it possible to react effectively and efficiently to failures, varying user demands, and changes in the application's execution environment. The resulting systems are highly concurrent and fault-tolerant, with minimal dependencies among individual system components.

 

 

Reactive Design Patterns is a clearly-written guide for building message-driven distributed systems that are resilient, responsive, and elastic. It contains 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—in some cases, Java, JavaScript, and Erlang. Software engineers and architects will learn patterns that address day-to-day distributed development problems in a fault-tolerant and scalable way. Project leaders and CTOs will gain a deeper understanding of the reactive design philosophy.

 

 

 

KEY FEATURES

 

Offers best patterns for building reactive applications

All patterns include concrete examples

Discover best practices

Explains theory behind reactive system design principles

 

AUDIENCE

Readers should be familiar with a standard programming language like Java, C++ or C# and be comfortable with the basics of distributed systems. Although most of the book's examples use the Scala language, no prior experience with Scala or Akka is required.

 

 

ABOUT THE TECHNOLOGY

The design patterns in this book were collected by the consultants and engineers of Typesafe during thousands of hours spent building enterprise-quality applications using Scala and Akka. Although many reactive patterns can be implemented using standard development tools like Java, others require the capabilities offered by a functional programming language like Scala and an Actor-based concurrency system like Akka.

 

 

SummaryReactive 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 TechnologyModern 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 BookReactive 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 InsideThe definitive guide to the Reactive ManifestoPatterns for flow control, delimited consistency, fault tolerance, and much moreHard-won lessons about what doesn''t workArchitectures that scale under tremendous loadAbout the ReaderMost examples use Scala, Java, and Akka. Readers should be familiar with distributed systems.About the AuthorDr. 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

Why Reactive? A walk-through of the Reactive Manifesto Tools of the trade

PART 2 - THE PHILOSOPHY IN A NUTSHELL

Message passing Location transparency Divide and conquer Principled failure handling Delimited consistency Nondeterminism by need Message flow

PART 3 - PATTERNS

Testing reactive applications Fault tolerance and recovery patterns Replication patterns Resource-management patterns Message flow patterns Flow control patterns State management and persistence patterns