This title is printed to order. This book may have been self-published. If so, we cannot guarantee the quality of the content. In the main most books will have gone through the editing process however some may not. We therefore suggest that you be aware of this before ordering this book. If in doubt check either the author or publisher’s details as we are unable to accept any returns unless they are faulty. Please contact us if you have any questions.
Are you an experienced Go developer that wants to be more productive? Do you want to write cleaner, faster, and easier to maintain code?
Then the Beyond Effective Go book series is for you.
This series is aimed at competent Gophers. It does not mess around with the basics but instead dives right into the daily problems that professional programmers face. Chiefly, how to write fast, robust applications and services that can be maintained and extended as requirements change.
Unlike most books, Beyond Effective Go focuses on the programmer and the code by addressing the four critical aspects of programming in Go - developer productivity, application performance, code quality, and depth of understanding of the language and tools.
This book, Part 1 of the series, focuses on achieving high-performance code. You will learn which aspects of your application or code to focus on and when. You will have a suite of tools, software patterns, and recipes at your disposal to make your life easier. After reading, you will:
Understand the differences between Concurrency and Parallelism. Identify and avoid concurrency issues like deadlock, starvation, livelock, and data races. Understand the various concurrency interaction patterns and be able to apply the one that best fits the problem at hand. Take a deep dive into Go's concurrency primitives and be able to apply them expertly but also avoid many of their gotchas. Be able to diagnose concurrency and performance issues using Go's profiler, execution tracing, and benchmarking tools. Be able to identify when code needs optimizing, what needs optimizing and how. Have a catalog of concurrency and performance patterns that you can quickly apply to your projects.
