Dropbox’s journey to using Go.
Go scheduler’s job is to distribute runnable goroutines over multiple worker OS threads that runs on one or more processors. In multi-threaded computation, two paradigms have emerged in scheduling: work sharing and work stealing. Go has a work-stealing scheduler since 1.1, contributed by Dmitry Vyukov. This article will go in depth explaining what work-stealing schedulers are and how Go implements one.
Every now and then I find developers struggling with handling time in their tests, so I wanted to address that in this blog post.
This post is a walk-through of the simple strace implementation I wrote during my GopherCon talk, A Go Programmer’s Guide to Syscalls. You’ll find the code here.
As a DevOps leader it’s up to you to balance the autonomy and flexibility of a DevOps approach with the business value it was meant to create by making all your pipeline tools more collaborative, integrated, and automated. But challenges arise when you have multiple instances of the same tool, different tools with overlapping functionality, no ability to collaborate across teams—all resulting in unknown bottlenecks and complicated or no reporting. Read this Gartner research note to learn how to patch any leaks in your DevOps.
There is a lot of material available about the pros and cons of Dependency Injection. This post is less about the pattern itself and more about its implementation design and it’s side-effects w.r.t Go.
Most of my work has been dealing with time series and market data. Speedy work across simple integers and floating point arrays suffices for a great majority of the work. Golang is a good fit there.
For the purpose of this tutorial, we’ll be creating a RESTful API for a Phone Book app.
To understand the uses of factory pattern and singleton pattern in real life application.
One of the common use case in Go is to start a few goroutines to do some work. These goroutines block listening in on a channel, waiting for more work to arrive. At some point, you want to signal these goroutines to stop accepting more work and exit, so you can cleanly shut down the program.
Oakmound Studio has been working on Agent Blue for over a year and has developed an Engine alongside the game. Today we are happy to announce that our engine Oak is now at a stable point where we have decided to finally open source it on github. The Oak engine provides the basis for Agent Blue from creating the screen all the way up to the particles and collision system.
gophercon 2017-talks - 87 Stars, 12 Fork
Slides and links for 2017 talks
etcdhcp - 80 Stars, 5 Fork
A DHCP server backed by etcd
protobuild - 14 Stars, 0 Fork
Build protobufs in Go, easily.
kubernetes-initializer-tutorial - 9 Stars, 0 Fork
Hands-on tutorial for building and deploying Kubernetes Initializers.
grpc-throttle - 3 Stars, 0 Fork
grpc-throttle interceptor for grpc server (goLang)