README
¶
Go kit
Go kit is a programming toolkit for building microservices (or elegant monoliths) in Go. We solve common problems in distributed systems and application architecture so you can focus on delivering business value.
- Website: gokit.io
- Mailing list: go-kit
- Slack: gophers.slack.com #go-kit (invite)
Sponsors
Encore – the platform for building Go-based cloud backends.
Click here or Sponsor, above, for more information on sponsorship.
Motivation
Go has emerged as the language of the server, but it remains underrepresented in so-called "modern enterprise" companies like Facebook, Twitter, Netflix, and SoundCloud. Many of these organizations have turned to 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, the motivating blog post and the video of the talk. See also the Go kit talk at GopherCon 2015.
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. Thank you, contributors!
Dependency management
Go kit is modules aware, and we encourage users to use the standard modules tooling. But Go kit is at major version 0, so it should be compatible with non-modules environments.
Code generators
There are several third-party tools that can generate Go kit code based on different starting assumptions.
- RecoLabs/microgen
- GrantZheng/kit
- kujtimiihoxha/kit (unmaintained)
- nytimes/marvin
- sagikazarmark/mga
- sagikazarmark/protoc-gen-go-kit
- metaverse/truss
- goadesign/goakit
Related projects
Projects with a ★ have had particular influence on Go kit's design (or vice-versa).
Service frameworks
- gizmo, a microservice toolkit from The New York Times ★
- go-micro, a distributed systems development framework ★
- gotalk, async peer communication protocol & library
- Kite, a micro-service framework
- gocircuit, dynamic cloud orchestration
Individual components
- afex/hystrix-go, client-side latency and fault tolerance library
- armon/go-metrics, library for exporting performance and runtime metrics to external metrics systems
- codahale/lunk, structured logging in the style of Google's Dapper or Twitter's Zipkin
- eapache/go-resiliency, resiliency patterns
- sasbury/logging, a tagged style of logging
- grpc/grpc-go, HTTP/2 based RPC
- inconshreveable/log15, simple, powerful logging for Go ★
- mailgun/vulcand, programmatic load balancer backed by etcd
- mattheath/phosphor, distributed system tracing
- pivotal-golang/lager, an opinionated logging library
- rubyist/circuitbreaker, circuit breaker library
- sirupsen/logrus, structured, pluggable logging for Go ★
- sourcegraph/appdash, application tracing system based on Google's Dapper
- spacemonkeygo/monitor, data collection, monitoring, instrumentation, and Zipkin client library
- streadway/handy, net/http handler filters
- vitess/rpcplus, package rpc + context.Context
- gdamore/mangos, nanomsg implementation in pure Go
Web frameworks
Additional reading
- Architecting for the Cloud — Netflix
- Dapper, a Large-Scale Distributed Systems Tracing Infrastructure — Google
- Your Server as a Function (PDF) — Twitter
Directories
¶
| Path | Synopsis |
|---|---|
|
auth
|
|
|
Package endpoint defines an abstraction for RPCs.
|
Package endpoint defines an abstraction for RPCs. |
|
Package log provides a structured logger.
|
Package log provides a structured logger. |
|
deprecated_levels
Package levels implements leveled logging on top of Go kit's log package.
|
Package levels implements leveled logging on top of Go kit's log package. |
|
level
Package level implements leveled logging on top of Go kit's log package.
|
Package level implements leveled logging on top of Go kit's log package. |
|
logrus
Package logrus provides an adapter to the go-kit log.Logger interface.
|
Package logrus provides an adapter to the go-kit log.Logger interface. |
|
syslog
Deprecated: Use github.com/go-kit/log/syslog instead.
|
Deprecated: Use github.com/go-kit/log/syslog instead. |
|
term
Package term provides tools for logging to a terminal.
|
Package term provides tools for logging to a terminal. |
|
Package metrics provides a framework for application instrumentation.
|
Package metrics provides a framework for application instrumentation. |
|
cloudwatch2
Package cloudwatch2 emits all data as a StatisticsSet (rather than a singular Value) to CloudWatch via the aws-sdk-go-v2 SDK.
|
Package cloudwatch2 emits all data as a StatisticsSet (rather than a singular Value) to CloudWatch via the aws-sdk-go-v2 SDK. |
|
discard
Package discard provides a no-op metrics backend.
|
Package discard provides a no-op metrics backend. |
|
dogstatsd
Package dogstatsd provides a DogStatsD backend for package metrics.
|
Package dogstatsd provides a DogStatsD backend for package metrics. |
|
expvar
Package expvar provides expvar backends for metrics.
|
Package expvar provides expvar backends for metrics. |
|
generic
Package generic implements generic versions of each of the metric types.
|
Package generic implements generic versions of each of the metric types. |
|
graphite
Package graphite provides a Graphite backend for metrics.
|
Package graphite provides a Graphite backend for metrics. |
|
influx
Package influx provides an InfluxDB implementation for metrics.
|
Package influx provides an InfluxDB implementation for metrics. |
|
influxstatsd
Package influxstatsd provides support for InfluxData's StatsD Telegraf plugin.
|
Package influxstatsd provides support for InfluxData's StatsD Telegraf plugin. |
|
internal/convert
Package convert provides a way to use Counters, Histograms, or Gauges as one of the other types
|
Package convert provides a way to use Counters, Histograms, or Gauges as one of the other types |
|
internal/ratemap
Package ratemap implements a goroutine-safe map of string to float64.
|
Package ratemap implements a goroutine-safe map of string to float64. |
|
multi
Package multi provides adapters that send observations to multiple metrics simultaneously.
|
Package multi provides adapters that send observations to multiple metrics simultaneously. |
|
prometheus
Package prometheus provides Prometheus implementations for metrics.
|
Package prometheus provides Prometheus implementations for metrics. |
|
provider
Package provider provides a factory-like abstraction for metrics backends.
|
Package provider provides a factory-like abstraction for metrics backends. |
|
statsd
Package statsd provides a StatsD backend for package metrics.
|
Package statsd provides a StatsD backend for package metrics. |
|
teststat
Package teststat provides helpers for testing metrics backends.
|
Package teststat provides helpers for testing metrics backends. |
|
Package transport contains helpers applicable to all supported transports.
|
Package transport contains helpers applicable to all supported transports. |
|
http
Package http provides a general purpose HTTP binding for endpoints.
|
Package http provides a general purpose HTTP binding for endpoints. |
|
util
|
|
|
conn
Package conn provides utilities related to connections.
|
Package conn provides utilities related to connections. |
Click to show internal directories.
Click to hide internal directories.