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!
Short answer: why not? Go is relatively easy to learn, not too verbose and there is a huge ecosystem of libraries which can be reused to avoid writing all the code from scratch.
Advanced Go debugging with Delve at FOSDEM 2018
Write a Kubernetes Ready Service with Go
if you have ever tried Go, you probably know that writing services with Go is an easy thing. Yes, we really need only few lines to be able to run http service. But what do we need to add if we want to prepare our service for production? Let’s discuss it by an example of a service which is ready to be run in Kubernetes.
The Ultimate Guide to Writing Dockerfiles for Go Web-apps
You probably want to use Docker with Go, because:
1. You have to work with different versions of Go on the same machine.
2. You need exact, reproducible, shareable and deterministic environments for development as well as production.
3. You need a quick and easy way of building and deploying a final compiled binary.
4. You might want to get started quickly (anyone with Docker installed can start coding right away without setting up any other dependencies or GOPATH variables).
Well, you’ve come to the right place. READ MORE
Elasticsearch query examples with Golang
Queries in Elastic differ quite a lot from standard (No)SQL ones. Even though the end result is pretty much the same (get all from table A, order by column B,C desc where column D like ‘E’) and you could easily draw a line between those two, the complexity of queries in Elastic is way much higher compared to SQL ones.
So just how fast are channels anyway?
The speed of channels isn’t really the point, but I couldn’t help but wonder how fast they are. So I wrote a benchmark!
An article aimed at beginners to understand how to compose more complex packages, beyond making the usual “one package - one binary” ones. You can check it out here.
Write your HTTP application in Go once, deploy it everywhere (on-premise & AWS Lambda supported)
Just call gluo.ListenAndServe
instead of http.ListenAndServe
.
package main
import (
"github.com/imdario/gluo"
"net/http"
)
func handler(w http.ResponseWriter, r *http.Request) {
w.Write([]byte("Hello from Gluo"))
}
func main() {
gluo.ListenAndServe(":3000", http.HandlerFunc(handler))
}
Buffalo Blog https://blog.gobuffalo.io/buffalo-v0-10-3-released-d871076013d1