122 lines
6.8 KiB
Markdown
122 lines
6.8 KiB
Markdown
|
# Go kit [](https://circleci.com/gh/go-kit/kit) [](https://travis-ci.org/go-kit/kit) [](https://godoc.org/github.com/go-kit/kit) [](https://coveralls.io/github/go-kit/kit?branch=master) [](https://goreportcard.com/report/go-kit/kit) [](https://sourcegraph.com/github.com/go-kit/kit?badge)
|
||
|
|
|
||
|
|
**Go kit** is a **distributed programming toolkit** for building microservices
|
||
|
|
in large organizations. We solve common problems in distributed systems, so
|
||
|
|
you can focus on your business logic.
|
||
|
|
|
||
|
|
- Website: [gokit.io](https://gokit.io)
|
||
|
|
- Mailing list: [go-kit](https://groups.google.com/forum/#!forum/go-kit)
|
||
|
|
- Slack: [gophers.slack.com](https://gophers.slack.com) **#go-kit** ([invite](https://gophersinvite.herokuapp.com/))
|
||
|
|
|
||
|
|
## Motivation
|
||
|
|
|
||
|
|
Go has emerged as the language of the server, but it remains underrepresented
|
||
|
|
in large, consumer-focused tech companies like Facebook, Twitter, Netflix, and
|
||
|
|
SoundCloud. These organizations have largely adopted JVM-based stacks for
|
||
|
|
their business logic, owing in large part to libraries and ecosystems that
|
||
|
|
directly support their microservice architectures.
|
||
|
|
|
||
|
|
To reach its next level of success, Go needs more than simple primitives and
|
||
|
|
idioms. It needs a comprehensive toolkit, for coherent distributed programming
|
||
|
|
in the large. Go kit is a set of packages and best practices, which provide a
|
||
|
|
comprehensive, robust, and trustable way of building microservices for
|
||
|
|
organizations of any size.
|
||
|
|
|
||
|
|
For more details, see
|
||
|
|
[the website](https://gokit.io),
|
||
|
|
[the motivating blog post](http://peter.bourgon.org/go-kit/) and
|
||
|
|
[the video of the talk](https://www.youtube.com/watch?v=iFR_7AKkJFU).
|
||
|
|
See also the
|
||
|
|
[Go kit talk at GopherCon 2015](https://www.youtube.com/watch?v=1AjaZi4QuGo).
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
|
||
|
|
- Operate in a heterogeneous SOA — expect to interact with mostly non-Go-kit services
|
||
|
|
- RPC as the primary messaging pattern
|
||
|
|
- Pluggable serialization and transport — not just JSON over HTTP
|
||
|
|
- Operate within existing infrastructures — no mandates for specific tools or technologies
|
||
|
|
|
||
|
|
## Non-goals
|
||
|
|
|
||
|
|
- Supporting messaging patterns other than RPC (for now) — e.g. MPI, pub/sub, CQRS, etc.
|
||
|
|
- Re-implementing functionality that can be provided by adapting existing software
|
||
|
|
- Having opinions on operational concerns: deployment, configuration, process supervision, orchestration, etc.
|
||
|
|
|
||
|
|
## Contributing
|
||
|
|
|
||
|
|
Please see [CONTRIBUTING.md](/CONTRIBUTING.md).
|
||
|
|
Thank you, [contributors](https://github.com/go-kit/kit/graphs/contributors)!
|
||
|
|
|
||
|
|
## Dependency management
|
||
|
|
|
||
|
|
Go kit is a library, designed to be imported into a binary package.
|
||
|
|
Vendoring is currently the best way for binary package authors
|
||
|
|
to ensure reliable, reproducible builds.
|
||
|
|
Therefore, we strongly recommend our users use vendoring for all of their dependencies,
|
||
|
|
including Go kit.
|
||
|
|
To avoid compatibility and availability issues,
|
||
|
|
Go kit doesn't vendor its own dependencies,
|
||
|
|
and doesn't recommend use of third-party import proxies.
|
||
|
|
|
||
|
|
There are several tools which make vendoring easier, including
|
||
|
|
[gb](http://getgb.io),
|
||
|
|
[glide](https://github.com/Masterminds/glide),
|
||
|
|
[gvt](https://github.com/FiloSottile/gvt),
|
||
|
|
[govendor](https://github.com/kardianos/govendor), and
|
||
|
|
[vendetta](https://github.com/dpw/vendetta).
|
||
|
|
In addition, Go kit uses a variety of continuous integration providers
|
||
|
|
to find and fix compatibility problems as soon as they occur.
|
||
|
|
|
||
|
|
## Related projects
|
||
|
|
|
||
|
|
Projects with a ★ have had particular influence on Go kit's design (or vice-versa).
|
||
|
|
|
||
|
|
### Service frameworks
|
||
|
|
|
||
|
|
- [gizmo](https://github.com/nytimes/gizmo), a microservice toolkit from The New York Times ★
|
||
|
|
- [go-micro](https://github.com/myodc/go-micro), a microservices client/server library ★
|
||
|
|
- [h2](https://github.com/hailocab/h2), a microservices framework ★
|
||
|
|
- [gotalk](https://github.com/rsms/gotalk), async peer communication protocol & library
|
||
|
|
- [Kite](https://github.com/koding/kite), a micro-service framework
|
||
|
|
- [gocircuit](https://github.com/gocircuit/circuit), dynamic cloud orchestration
|
||
|
|
|
||
|
|
### Individual components
|
||
|
|
|
||
|
|
- [afex/hystrix-go](https://github.com/afex/hystrix-go), client-side latency and fault tolerance library
|
||
|
|
- [armon/go-metrics](https://github.com/armon/go-metrics), library for exporting performance and runtime metrics to external metrics systems
|
||
|
|
- [codahale/lunk](https://github.com/codahale/lunk), structured logging in the style of Google's Dapper or Twitter's Zipkin
|
||
|
|
- [eapache/go-resiliency](https://github.com/eapache/go-resiliency), resiliency patterns
|
||
|
|
- [sasbury/logging](https://github.com/sasbury/logging), a tagged style of logging
|
||
|
|
- [grpc/grpc-go](https://github.com/grpc/grpc-go), HTTP/2 based RPC
|
||
|
|
- [inconshreveable/log15](https://github.com/inconshreveable/log15), simple, powerful logging for Go ★
|
||
|
|
- [mailgun/vulcand](https://github.com/vulcand/vulcand), programmatic load balancer backed by etcd
|
||
|
|
- [mattheath/phosphor](https://github.com/mondough/phosphor), distributed system tracing
|
||
|
|
- [pivotal-golang/lager](https://github.com/pivotal-golang/lager), an opinionated logging library
|
||
|
|
- [rubyist/circuitbreaker](https://github.com/rubyist/circuitbreaker), circuit breaker library
|
||
|
|
- [Sirupsen/logrus](https://github.com/Sirupsen/logrus), structured, pluggable logging for Go ★
|
||
|
|
- [sourcegraph/appdash](https://github.com/sourcegraph/appdash), application tracing system based on Google's Dapper
|
||
|
|
- [spacemonkeygo/monitor](https://github.com/spacemonkeygo/monitor), data collection, monitoring, instrumentation, and Zipkin client library
|
||
|
|
- [streadway/handy](https://github.com/streadway/handy), net/http handler filters
|
||
|
|
- [vitess/rpcplus](https://godoc.org/github.com/youtube/vitess/go/rpcplus), package rpc + context.Context
|
||
|
|
- [gdamore/mangos](https://github.com/gdamore/mangos), nanomsg implementation in pure Go
|
||
|
|
|
||
|
|
### Web frameworks
|
||
|
|
|
||
|
|
- [Gorilla](http://www.gorillatoolkit.org)
|
||
|
|
- [Gin](https://gin-gonic.github.io/gin/)
|
||
|
|
- [Negroni](https://github.com/codegangsta/negroni)
|
||
|
|
- [Goji](https://github.com/zenazn/goji)
|
||
|
|
- [Martini](https://github.com/go-martini/martini)
|
||
|
|
- [Beego](http://beego.me/)
|
||
|
|
- [Revel](https://revel.github.io/) (considered [harmful](https://github.com/go-kit/kit/issues/350))
|
||
|
|
|
||
|
|
## Additional reading
|
||
|
|
|
||
|
|
- [Architecting for the Cloud](http://fr.slideshare.net/stonse/architecting-for-the-cloud-using-netflixoss-codemash-workshop-29852233) — Netflix
|
||
|
|
- [Dapper, a Large-Scale Distributed Systems Tracing Infrastructure](http://research.google.com/pubs/pub36356.html) — Google
|
||
|
|
- [Your Server as a Function](http://monkey.org/~marius/funsrv.pdf) (PDF) — Twitter
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
Development supported by [DigitalOcean](https://digitalocean.com).
|