Our tradition at Gopher Academy is to host an Advent Calendar of blog posts contributed by the community each December. I’m excited to kick off the 2019 series with this introduction!
I wrote a quick introduction about why I think reactive planning is a cloud native pattern and I published an article about control theory, but I have just scratched the surface of this topic obviously.
There are a lot of information in the title I know, but I am not good enough to make it simple.
Back in the days, I tried to make some contribution to OpenZipkin an open source tracing infrastructure in Java.
We love taking photos. Privacy concerns - and the wish to properly archive them for the next generation - brought us to the conclusion that existing cloud solutions are not the right tool to keep them organized.
The Go Garbage Collector (GC) works exceptionally well when the amount of memory allocated is relatively small, but with larger heap sizes the GC can end up using considerable amounts of CPU.
== Using Go for DevOps ==
This post is aiming to provide a new angle on using Go. Don’t expect code snippets or learning a new thing, but rather be open for a new perspective, and share this with your favorite SysOps/DevOps/Observability Engineers who are considering new solutions.
