- Paperback: 448 pages
- Publisher: Manning Publications; 1 edition (September 30, 2016)
- Language: English
- ISBN-10: 1617291013
- ISBN-13: 978-1617291012
- Product Dimensions: 7.3 x 0.9 x 9.1 inches
- Shipping Weight: 1.7 pounds (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #551,312 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.
Akka in Action 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
Raymond Roestenburg is an experienced software craftsman, polyglot programmer, and software architect. He is an active member of the Scala community, an Akka committer, and contributed to the Akka-Camel module.
Rob Bakker is an experienced developer focused on concurrent back-end systems and system integration. He has used Scala and Akka in production from version 0.7.
Rob Williams is founder of ontometrics, a practice that has been focused on Java solutions that include machine learning. He first used Actor-based programming a decade ago, and found Akka while looking for someone who had given thought to the idea of supervision, and has used it for several projects since.
Showing 1-8 of 8 reviews
There was a problem filtering reviews right now. Please try again later.
My thanks to Manning for providing an advance reading copy for review.
Chapter 2 dives straight into some complex code without explaining much. You'll infer things like ! is how actors send fire-and-forget messages, but the book should explain basics like this
Next chapter is TDD and I'm not sure why this is the so early in the book. I still want to learn the fundamentals and we're testing already
Chapter 6 is on remoting but I didn't want to go that deep yet. Still looking more for fundamentals.
The authors provided a lot of code to accompany this book. It is available on github and I was trivial to setup and run with Intellij. You don't even need an IDE however as SBT is a very powerful tool (REPL and runner) from the command-line.
It would have been nice to see a hello-world example, and there is something of that nature but you need to skip all the way to Chapter 7. So again, the flow of the book could have been better thought out IMO. One minor annoyance is some of the examples, like the REPL Remoting are an image in the book, so you have to type it out by hand, ie, no cut and paste.
found a typo:
"But the problem with these properties is that you never know for sure that these properties exit."
Also found other typos, so a bit careless in editing here. I guess one aspect of reading a just published book is being a proofreader for the editor, sigh.
I've been reading with the online Google Books reader in epub format. I really like this since I can add notes and have all my books in one place (Kindle reader on Mac only works with Kindle purchased books and not all books are available in on Kindle, and many are not, like all Manning books!). The epub format has been good but at least one table was all garbled and I had to resort to the PDF version, and the images (tables) don't scale as well as the text so I end up squinting.
The writing style is just ok, sometimes a bit awkward. Hoping it will get better
It could have been a great book if 1) it used simple and precise language (e.g., "which takes two argument lists", did you mean two arguments?) and 2) it did not have typos in code and results.
Both these errors will slow down reading and comprehension; specifically, for folks who are not well-versed with Scala. To be fair, the book does say reader should know some Scala. However, I think the book would have been more accessible to non-Scala devs (e.g., Kotlin devs) if they wouldn't have to look up if a specific nuance was a typo or otherwise.
Also, all of the code bits are not in the book. While this is generally fine, I felt that some important code bits were missing and this slowed down reading and comprehension.