gphat

Hello! I'm the original author of Veneur @ Stripe and continue to work on it with a host of marvelous teammates.

I can't speak for the industry, but here's why I chose it for this project:

* I hadn't yet written anything in Go and wanted to try it on a side project / experiment

* I knew that my eventual deploy target (if the project turned out useful) would be lots of machines and I wanted to minimize the deployment requirements. Static binaries are good for that.

* I wanted to distribute the work across many cores and felt that Go's channels would make be a useful mechanism.

* I benchmarked my initial PoC against some other implementations (Python and JVM/Scala) and found no major reason to not use Go

The contributions of Stephen Jung (https://github.com/tummychow) and Aditya Mukerjee (https://github.com/chimeracoder) elevated it from a glimmer in my eye to system you can trust across your infrastructure.

So, in summary it was a confluence of interest and convenience with a strong hint of "if I use, this, it needs to be easy to deploy" and here we are 2 years later. :)

That's a good perspective. It's not for everyone. I didn't touch on that in my post, but it's important. I maintain a pretty rigid schedule and it's not been a problem at this job.

A reason I'm well suited is perhaps many years of ops and on-call work. I am not necessarily at my desk banging out code all day and night but weekend and middle-of-the-night emergencies are nothing new.

I also have a spouse who very much believes in me being happy. She's been really great in this process too.

Thanks for your comments!