Book Image

Hands-On High Performance with Go

By : Bob Strecansky
Book Image

Hands-On High Performance with Go

By: Bob Strecansky

Overview of this book

Go is an easy-to-write language that is popular among developers thanks to its features such as concurrency, portability, and ability to reduce complexity. This Golang book will teach you how to construct idiomatic Go code that is reusable and highly performant. Starting with an introduction to performance concepts, you’ll understand the ideology behind Go’s performance. You’ll then learn how to effectively implement Go data structures and algorithms along with exploring data manipulation and organization to write programs for scalable software. This book covers channels and goroutines for parallelism and concurrency to write high-performance code for distributed systems. As you advance, you’ll learn how to manage memory effectively. You’ll explore the compute unified device architecture (CUDA) application programming interface (API), use containers to build Go code, and work with the Go build cache for quicker compilation. You’ll also get to grips with profiling and tracing Go code for detecting bottlenecks in your system. Finally, you’ll evaluate clusters and job queues for performance optimization and monitor the application for performance regression. By the end of this Go programming book, you’ll be able to improve existing code and fulfill customer requirements by writing efficient programs.
Table of Contents (20 chapters)
Section 1: Learning about Performance in Go
Section 2: Applying Performance Concepts in Go
Section 3: Deploying, Monitoring, and Iterating on Go Programs with Performance in Mind

Understanding naming in Go

There are a lot of consistent behaviors that Go programmers like to retain in order to keep readable, maintainable code. Go naming schemes tend to be consistent, accurate, and short. We want to create names with the following idioms in mind:

  • Local variables for iterators should be short and simple:
    • i for an iterator; i and j if you have a two-dimensional iterator
    • r for a reader
    • w for a writer
    • ch for channels
  • Global variable names should be short and descriptive:
    • RateLimit
    • Log
    • Pool
  • Acronyms should follow the convention of using all capitals:
    • FooJSON
    • FooHTTP
  • Avoid stuttering with the package name:
    • log.Error() instead of log.LogError()
  • Interfaces with one method should follow the method name plus the -er suffix:
    • Stringer
    • Reader
    • Writer
    • Logger
  • Names in Go should follow a Pascal or mixedCaps case method:
    • var ThingOne
    • var thingTwo