- Paperback: 392 pages
- Publisher: Manning Publications; 1 edition (March 5, 2017)
- Language: English
- ISBN-10: 1617291803
- ISBN-13: 978-1617291807
- Product Dimensions: 7.3 x 0.7 x 9.2 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 4.2 out of 5 stars See all reviews (3 customer reviews)
- Amazon Best Sellers Rank: #244,878 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Reactive Design Patterns 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
About the Author
Dr. Roland Kuhn leads the Akka team at Typesafe. Together with Martin Odersky and Erik Meijer, Roland presented the Coursera course Principles of Reactive Programming and co-authored the Reactive Manifesto.
Brian Hanafee is a Principal Systems Architect at a large financial institution, with experience building reliable and secure web-based applications and backing services for millions of customers.
Jamie Allen is the Director of Consulting for Typesafe and author of Effective Akka.
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
1 Why Reactive?
2 A walk-through of the Reactive Manifesto
3 Tools of the trade
4 Message passing
5 Location transparency
6 Divide and conquer
7 Principled failure handling
8 Delimited consistency
9 Nondeterminism by need
10 Message flow
11 Testing reactive applications
12 Fault tolerance and recovery patterns
13 Replication patterns
14 Resource-management patterns
15 Message flow patterns
16 Flow control patterns
17 State management and persistence patterns
Of course I will update this review once I get a better idea of the book.
For now, I am not very satisfied: the book is quite verbose and uses a lot of words for introducing very basic concepts. Moreover, I would expect it to be more precise, better distinguishing concepts and explaining the ideas in a more compact and punctual way. I also perceive some redundancy (e.g., consider the following subsection titles in first 3 chapters: "1.3 Making the system responsive", "2.1 Reacting to users", "3.3 Responsiveness to users"). In other words, I deem Parts 1 and 2 not very effective. It is true that it says "This book does not require prior knowledge of Reactive systems", but I would have preferred a more advanced stance (e.g., à la GOF Design Patterns). But I do have quite a lot expectations for Part 3, about patterns :)