Book Image

Network Automation with Go

By : Nicolas Leiva, Michael Kashin
Book Image

Network Automation with Go

By: Nicolas Leiva, Michael Kashin

Overview of this book

Go’s built-in first-class concurrency mechanisms make it an ideal choice for long-lived low-bandwidth I/O operations, which are typical requirements of network automation and network operations applications. This book provides a quick overview of Go and hands-on examples within it to help you become proficient with Go for network automation. It’s a practical guide that will teach you how to automate common network operations and build systems using Go. The first part takes you through a general overview, use cases, strengths, and inherent weaknesses of Go to prepare you for a deeper dive into network automation, which is heavily reliant on understanding this programming language. You’ll explore the common network automation areas and challenges, what language features you can use in each of those areas, and the common software tools and packages. To help deepen your understanding, you’ll also work through real-world network automation problems and apply hands-on solutions to them. By the end of this book, you’ll be well-versed with Go and have a solid grasp on network automation.
Table of Contents (18 chapters)
1
Part 1: The Go Programming Language
6
Part 2: Common Tools and Frameworks
10
Part 3: Interacting with APIs

Go Proverbs

Rob Pike introduced the Go language proverbs at Gopherfest in 2015 to explain or teach Go philosophically. These are general guidelines that Go developers tend to adhere to. Most of these proverbs are good practices – but optional – that convey the spirit of the language.

We only include our favorite proverbs here. You can check out the full list at Go Proverbs (Further reading):

  • Gofmt's style is no one's favorite, yet gofmt is everyone's favorite. When you write code in Go, you don't have to worry about the debate of white spaces versus tabs, or where you put braces or curly brackets. Gofmt (gofmt) formats your code with a prescriptive style guide, so all Go code looks the same. This way, you don't have to think about it when you write or read Go code:
  • Clear is better than clever: Go favors clear code over clever code that is difficult to analyze or describe. Write code other people can read and with behavior they can understand.
  • Errors...