What does HackerNews think of kit?

see also: https://github.com/go-kit/kit

Or see also: https://medium.com/code-zen/why-i-don-t-use-go-web-framework... (or any of the dozens of blogs of people indicating why you dont need a framework for go)

Any ideas how this compares with [go-kit](https://github.com/go-kit/kit)?

I like how go-kit's transport not just JSON and HTTP (e.g. gRPC and protobufs are supported).

On the Go side take a look at go-kit

https://github.com/go-kit/kit

You can get a lot of boilerplate out of the box, and it's not hard to extend it with more sophisticated features like custom server timeouts.

The New York Times has a nice set of Go microservice frameworks with simple server boilerplate also:

https://github.com/NYTimes/gizmo

Currently using gokit: https://github.com/go-kit/kit

Really nice interface for adding tracing, middleware/finalizer logging/metrics, circuit-breakers, etc to your application.

Sqlx and go-kit are two libraries that helped while learning Go. Sqlx helped me understand the value of Go's implicit interfaces/package level structure, while go-kit helped me better understand good project structure.

https://github.com/jmoiron/sqlx https://github.com/go-kit/kit

HashiCorp put out good stuff. CoreOS can be hit or miss; Torus was nice, etcd is a wreck. I like https://github.com/go-kit/kit and https://github.com/oklog/oklog. Definitely avoid Kubernetes and Docker -- they're Go by committee, look and feel like transliterated Java.

I think this is heading towards what you're looking for: https://github.com/go-kit/kit