Roman Dodin
I assume you are already into Go, and you want to see how Go can apply to the network automation problem space, or you’re curious to know why Go for network automation. Allow me to share why I once switched to Go, what were the main drivers for that move, and why I think it is a perfect time for network engineers to start looking at Go.
Before delving into Go, I used Python for all things network automation; no big surprises here. For the past couple of decades, the usual network automation workflow revolved around crafting/templating CLI commands, sending them over...