Go in Practice guides you through dozens of real-world techniques in key areas like package management, microservice communication, and more. Following a cookbook-style Problem/Solution/Discussion format, this practical handbook builds on the foundational concepts of the Go language and introduces specific strategies you can use in your day-to-day applications. You'll learn techniques for building web services, using Go in the cloud, testing and debugging, routing, network applications, and much more.
1. This is NOT a book for you, if you want to learn Golang basics. That's very good, as there are some introductory level books already present and they are of very reasonable quality. 2. This is NOT a book for you, if you want to explore truly advanced topics about Golang. Such a book doesn't exist - language is still evolving & if you're interested you always have an option to collaborate on-line, Google & language creators are very open & encourage you to do so. 3. This IS a book FOR YOU, if you already know the language & are interested in learning how to write idiomatic Golang, how to address the most common problems (in a most suitable way), how to grasp the essence & individual, unique flavor of the language.
OK, but enough about the intentions of the authors - does the book actually succeed in making the goal? Yes, but ... it leaves a reader a bit unsatisfied -> each topic (like error handling, logging, exposing services, etc.) starts in a very encouraging way, but leaves the job half-way there. In other ways - it helps you getting started, but several questions remain. This applies to pretty much every chapter. I know that it's just not feasible to contain everything in the book, but I can't help being slightly disappointed after the read. What is more, some chapters (e.g. 7, 9, 10) felt a little bit like gap fillers.
To summarize: it's a nice addition to "Go in Action", but you'll manage w/o it. There's plenty of material on the web you can compensate with.
Go in Practice is a nice small book that in my opinion should be the starting point for every Golang programmer. As the language is so small you can learn it in a few days, but its libraries are its biggest value if you ask me and this book tries to explain why those libraries have allowed to scaffold such projects as Docker and Kubernetes.
The book is boring sometimes, it goes in too much detail without a particular need. Explaining the methods of this or that class is too much of a burden for the readers in my opinion.
The biggest flaw of the book is also its biggest virtue. Even though I had no problems with running some of the code that's embedded in the book ( the version of the book in Safari is awful BTW) as the book promises to be a practical guide some the solutions to the problems the author thinks one can face are a bit outdated. If you claim to give practical solutions than you need to update your book with the best solution that's currently available
in short: * This is not the book you want to learn Go from * This is not a book you want to read from start to finish. * some of content are outdated relative to today best practice.
Other than very small part in start of each chapter, 90% of book filled with 70 problems and solution to them. Most of problems are good and solution are explained well but real problem is book itself. This is like that you pick 70 question and answers in Go section of Stack Overflow, edit them and print it as a book. This is best I can describe format of this book. You probably don't face with some of the problems in you own work even afters years of writing Go and certainly encounter a lot of other problems that not covered in this book. why someone spend money on this when (s)he can google each time that have a problem and find answers easier and faster than trying to find in a book, even if it's available.
This book is one of the more frequently recommended books on go and because it's not a total beginners book it sounded really good for my case. It contains some good content (I especially liked the chapter on reflection) and is well written but I was still a bit disappointed. It's very close to a cookbook, describing solutions to specific problems. Sometimes this can be repetitive, after learning how to parse a single file upload I don't necessarily need another section to learn how to parse multiple uploaded files. I also missed some content like how to properly structure programs using functions, types and packages.
Can't say this book is deep and really into theoretical basis of Go - but it's a very practical guide how to solve typical problems in go, such as loggin, IPC, servicing and so on.
If you want to dig deeper in go itself - it's better to read Kernigan's one (book with the bridge on cover)
Книга может быть полезна действующим golang программистам, чтобы сравнить свои практики с рекомендуемыми. Описание структур данных и команд было бы полезно, и незначительно бы повлияло на объем. В целом книге не хватает концептуальных идей, все слишком конкретно.