Made a library? Written a blog post? Found a useful tutorial? Share it with the Go community here or just enjoy what everyone else has found!
The Go language is great for concurrency, but when you have to do work that is naturally serial, must you forgo those benefits? We faced this question while rewriting our database backup utility, mongodump, and utilized a “divide-and-multiplex” method to marry a high-throughput concurrent workload with a serial output.
PegoMock is a mocking framework for the Go programming language. It integrates well with Go's built-in
testing package, but can be used in other contexts too. It is based on golang/mock, but uses a DSL closely related to Mockito.
Lottip is proxy for MySQL RDBMS with web GUI. It will show you what's happening under the hood of your database layer. As it sits between your application and MySQL server there's no need to use tools like Wireshark or enable general logs to see which queries are being executed. It comes as single binary with zero dependencies and consists of 2 parts: proxy server and embedded GUI. https://github.com/orderbynull/lottip
fakedata - a small Go program for random data generator. Lots of goodies in this release!
HyperLogLog with lots of sugar (Sparse, LogLog-Beta bias correction and TailCut space reduction).
An improved version of HyperLogLog for the count-distinct problem, approximating the number of distinct elements in a multiset using 20-50% less space than other usual HyperLogLog implementations.
zerolog - The zerolog package provides a fast and simple logger dedicated to JSON output.
Zerolog's API is designed to provide both a great developer experience and stunning performance. Its unique chaining API allows zerolog to write JSON log events by avoiding allocations and reflection.
In this video we’ll build a Buffalo application that uses Goth to add authorization using GitHub.
This video will demostrate the following:
What is idiomatic Go? It's frequently asked, but doesn't have an easy answer. Part of the problem is that we are still figuring it out. This is partly because Go is a young language. As the language and community matures, so will the idioms.
Be aware that idioms are more like guidelines than rules. Working code is more important than idiomatic code. Since idioms are sort of a shared experience, something that is not idiomatic is not necessarily wrong.
Since there isn't a definitive answer, I have collected relevant references.