Go 1.7 is out. One of the big features is the new SSA based compiler. The article below describes some of the tooling around this new feature.
Looking at your program’s structure in Go 1.7
The Go project does a great job of tooling.
If you into networking or specifically P4 you should take a look at the recent P4 workshop presentations.
A while ago the Packet Pushers had Geoff Huston on as a guest in the future of networking series. There are lots of good ideas and contrarian opinions in that podcast episode – go listen to it.
During the episode, Geoff mentioned a book that had a big influence on him called An Engineering Approach to Computer Networking. Naturally, I ordered a copy.
The first thing you’ll notice reading this book is that some aspects are dated – it was written in 1996 after all. This becomes obvious early on when ATM is mentioned as the likely replacement for Ethernet and how it will play a major role in the future – obviously that didn’t work out.
Fortunately, most of the content is much more timeless.
Almost all networking books that try to be computer science or engineering text books are much closer to being descriptions of how IP networking works vs. really teaching the science behind networking. This book is the opposite – it’s not the book to read if you want to win an IP networking quiz show.
The principles discussed throughout the book underlie all circuit and packet switched networks so digging into details that may seem out of date is still well worth the time. This helps to build a solid foundation and gives a bit of perspective on how and why so much has stayed the same.
I’m not going to bother giving this book any kind of rating. If you have an interest in computer networking you should read it. For an even more abstract and science based view of computer networking you should also read my favourite networking book – Patterns in Networking Architecture.
At work we’ve started to instrument our micro-services with Prometheus. The combination of Prometheus and Grafana is pretty amazing.
One of the nice things Prometheus does is auto-discovery of services in a Kubernetes cluster. The docs for this area aren’t bad but I couldn’t find a complete example so here’s the configuration we use.
- job_name: 'kubernetes'
kubernetes_sd_configs:
- api_servers:
- 'https://kubernetes.default.svc'
in_cluster: true
relabel_configs:
- regex: "__meta_kubernetes_role"
action: labelmap
replacement: "kubernetes_role"
- regex: "__meta_kubernetes_node_label_(.*)"
action: labelmap
replacement: "kubernetes_node_label_${1}"
- regex: "__meta_kubernetes_service_namespace"
action: labelmap
replacement: "kubernetes_service_namespace"
- regex: "__meta_kubernetes_service_name"
action: labelmap
replacement: "kubernetes_service_name"
- regex: "__meta_kubernetes_service_label_(.*)"
action: labelmap
replacement: "kubernetes_service_label_${1}"
- regex: "__meta_kubernetes_service_annotation_(.*)"
action: labelmap
replacement: "__meta_kubernetes_service_annotation_${1}"