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
Preface;Who This Book Is For;What Problems Are We Solving with Akka?;Reactive Applications;Use Case for This Book: Banking Service for Account Data;Conventions Used in This Book;Using Code Examples;Safari? Books Online;How to Contact Us;Acknowledgments;Chapter 1: Actor Application Types;1.1 Domain-driven;1.2 Work Distribution;Chapter 2: Patterns of Actor Usage;2.1 The Extra Pattern;2.2 The Cameo Pattern;Chapter 3: Best Practices;3.1 Actors Should Do Only One Thing;3.2 Avoid Blocking;3.3 Avoid Premature Optimization;3.4 Be Explicit;3.5 Dont Expose Actors;3.6 Help Yourself in Production;3.7 Tune Akka Applications with the Typesafe Console;Colophon;
Jamie Allen is the Director oflă#