- Paperback: 521 pages
- Publisher: Artima Inc (24 May 2013)
- Language: English
- ISBN-10: 0981531660
- ISBN-13: 978-0981531663
- Product Dimensions: 3.2 x 17.8 x 22.9 cm
- Average Customer Review: 3.8 out of 5 stars See all reviews (4 customer reviews)
- Amazon Bestsellers Rank: 256,704 in Books (See Top 100 in Books)
AKKA Concurrency Paperback – 24 May 2013
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
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 e-mail address or mobile phone number.
More About the Author
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
The chapter on Akka FSM alone makes this book worth the money.
I will wait for the Akka in Action book due out on 3 Mar 2015 by Raymond Roestenburg (Author), Rob Bakker (Author), Rob Williams (Author). Hopefully that will be a more serious and non-trivial attempt at explaining how to use this framework.
Most Helpful Customer Reviews on Amazon.com (beta)
Akka is a wonderful framework that allows designing asynchronous non blocking distributed applications. The literature covering Akka and reactive programming is scarce and fragmented. The examples online are limited and often uninteresting. The "best practices" or "patterns" of Akka programming are only very briefly documented in the Akka online documentation.
This book could have filled all of those gaps by being both an introductory guide to actor programming and a reference guide for advanced patterns and concepts like actor supervision and self-healing, routing, remoting, clustering (actually not covered because not finalized at the time the book was published).
Instead, the author gets lost in his own sense of humor and horribly unpractical and contrived example (as others have noticed) that not only doesn't help understanding any pattern or best practice, but it also makes the first steps in actor programming much harder because it's too abstract and meaningless to give the reader some simple "real life" examples to work from.
Instead, the reader has to do the extra work of abstracting the concepts out of the (annoyingly "funny") text and the non-sense monolithic example (for which no complete source code is given, which makes it even harder to follow) and try to figure out how those concepts actually apply to a real system design, e.g., how to interact with a (blocking) database driver or other service, how and where to implement fault tolerance for the most critical parts of the system, how to distribute actors or actor systems across many machines for high availability, etc. None of this is covered with clarity in the book.
Moreover, the book isn't able to make a solid case for reactive programming and Akka by focusing on the unpractical code examples but also by lacking a clear and concise explanation of the advantages of non-blocking paradigms vs more traditional approaches.
I was expecting much more out of this. A much better book is Effective Akka by Jamie Allen (Effective Akka Jamie Allen which gives concise coding examples, spells out the advantages of reactive programming and its typical use cases, provides usable patterns and best practices in the form of real life code bits and simple and focused design recommendations. I was able to start designing my system after reading just a few pages of that book, while I got nowhere reading Akka Concurrency.
Here is one of it from the book...
"We've come to the second great axis of Akka's concurrency paradigm, the future. Futures have been around for a while now, but you've probably never seen them like this. These are futures on steroids; tiger steroids, laced with the blood of Superman, dripping with the testosterone of Batman, and infused with the power of Green Lantern's Ring. If you're not ready to have your brain set on fire, close this book, curl up in the fetal position, and sing Twinkle, Twinkle Little Star softly to yourself until you're good to go." - Chapter 12.
This makes it quite verbose and provide too much deviation from the subject matter.
Publisher, please review the text before you print. You have published great books like "Programming in Scala", and this is an excellent topic to have a book; but badly written book!