Using Go in DevOps
Looking at recent observability and operations tools, many are written in Go like Docker, Kubernetes or Prometheus. But why Go? Natalie Pistunovich explains in this DevOpsCon session.
Go is not a language traditionally used in SysOps. However, as SysOps transforms to DevOps and systems complexity keeps increasing, the need for scalability is increasing as well.
Scalable systems need generalized support, less scripting, and more software development, ideally using a cross-platform language that supports concurrency and parallelism. This is a great time to refresh the toolbox. Looking at recent observability and operations tools, many are written in Go: Docker, Kubernetes, Prometheus, CoreOS, Istio, Grafana, Jaeger, Moby, etc.
Why Go?
In this talk, Natalie Pistunovich goes over the general characteristics of the language, when its use makes sense and what features make it a good choice, e.g. type safety, clear syntax designed for concurrency, built-in support for parallelism, and the built-in cross-platform and cross-architecture support that doesn’t require dependencies management.
qewöihe
qwäieh
below: Interactive resource monitor for modern Linux systems
with Daniel XU | Facebook
“I Work Better Alone” and Other Lies You Tell Yourself
with Casie Siekman | soona
qwoieph
Yes, Golang is great for real-world web apps. It is wonderfully suited for commercial applications due to its easy to code readability and maintenance. Fewer lines of code mean quicker development and fast go-to-market. Inbuilt error checking allows for bug-free applications. There is a host of other advantage that ensures commercial viability.