I could barely reach the end of this book. I have hardly seen any book that was so boring to read. Most of the book’s CF examples didn’t work for me. Not to mention that some of the services this book is describing have evolved so much that this book will do you more harm than good if you’ll start using those services based on the book.
Apart from the last 4 chapters I reckon that this book could help you quickly brush up your AWS skills.
The last 4 chapters are still relevant. Even though I’d love to see more emphasis on Elastic BeansTalk, as well as it’s a great pity that though the authors have mentioned AWS Lambda&Gateway API that’d preferred to simply ignore it since it wasn’t available in all regions at the time.
As Docker continues to keep its pace as a constantly evolving technology, there’s no book that encompasses all aspects of it. In my opinion, this book came close to that. Though sometimes it doesn’t provide you all technical details it covers a lot of what you need to deal with Docker on a daily basis.
I found the examples that come with the book are so helpful that even sometimes I could even use them in order to improve some aspects of my daily routine.
The book covers docker 1.8, which API hasn’t changed so much since the book has been written. But some of the networking APIs, docker compose has slightly changed which allows to give this book only 4 stars. Apart from that it’s not a constantly updated book I can recommend it to anyone who considers Docker as a viable technology.
I’ve started reading this book as a draft long before it was released. I’ve abandoned it for a while, but this fall it was finally released thus I no other excuse to finally finish reading it.
I need to confess that’s not the first Akka book I’ve read so far. By no means this book covers all the aspects of Akka (which is enormously huge, albeit allows you to write full fledged applications based only on itself). But it is THE BOOK I would recommend you to read if you’re interested in Akka right now. The book has been recently updated to reflect the latest changes in http, persistence and some other modules. Taking into account how quickly does akka keep its pace I would say that after a while without constant updates (which took this book 4 years to get finished) this book could get outdated.
It has the bulk of the info you need to know about Akka to start working with it and get productive. Code that comes on its Github really works (which is rare for books’ code examples) and it can help you get your hands dirty in parts of the AKKA as quickly as possible.
My score is 4/5(I recommend to start reading it right now until it’s too late)
First things first. This book is 5 years old. FIVE YEARS! During this period of time Scala as a language has been evolving with a noticeable speed.
Is it still relevant? Yes, it is. Apart from a few chapters that’s dedicated to Actors and collections this book still contains a lot of useful information for an avid Scala-newbie.
Am I kidding? Not really. The explanation of type classes that’s inside of this book is the best that I’ve ever seen.
Even if you don’t see a reason to read the book from cover to cover I would recommend to skim through the “Type system” & “Using implicits” chapters. They’re highly comprehensive and will provide you with information that’ll definitely make your life as a Scala developer easier.
End of June: the same procedure as every year: On a former Russian military airfield. In the middle of nowhere in the fields of northern Germany. FUSION arises, the biggest holiday camp all over the nothern hemisphere! The motto: 4 days of ‘holiday communism’ – and the programme covers it all:
Music of all kinds, theatre, performance and cinema, and added in the whole spectrum of installations, interaction, arts and communication. Diversity of people, diverse in their intentions. Still, their strive for individual freedom unites them, everybody finding her and his own way of action. Free of boundaries and prejudice.
Disclaimer: The book that I’ve read is the newest edition available at safari
I’m not even sure whom this book is dedicated to. If you’re a Scala developer then this book is too outdated due to that most of the APIs it explains are either deprecated of heavily rewritten. If you’re a DevOps… well, you don’t read books at all. You can definitely use it as a reference for some of the SBT commands, but there’re lots of such references available on the Internet with convenient search by word as well as code examples.
You would definitely find another thing to spend your money on than buying this book.
This book has an outstanding goal – teaching FP principles to those who might have close to no experience with functional programming. I reckon that’s not doable during the coarse of a few hundred pages. Fortunately, this book delivers that what it has promised.
All the book’s materials are split into the chunks of textual information and exercises you’re encouraged to do in order to fully absorb all the meaningful information you might otherwise forget in a day.Since starting to read I understood a lot of concepts that previously I thought of as too complex for me which made my life a lot easier and my code better.
Unfortunately, I’ve found that the most important parts of the book were 5 first chapters as well as 3 last chapters. Besides these chapters I got lost trying to digest some of the concepts that this book has tried to teach me. Apparently that has something to do with the amount of exercises you need to complete to make a progress with this book. I’ve spent more than 2 months in reading and doing the book’s exercises, which was a real exhaustive experience and made me glad that finally I’ve finished this book without abandoning it due to frustration.
My score is 4/5. Authors need to grasp more teaching experience to make their book easier to comprehend and get rid of some useless exercises but keep all the important ones.