README
¶
gokit
gokit is a working name for a distributed programming toolkit to serve the needs of the modern service-oriented enterprise.
- GitHub repository -- RFCs, issues, PRs, etc.
- go-kit mailing list
- Freenode #gokit
Motivation
See the motivating blog post and the video of the talk.
Goals
- Operate in a heterogeneous SOA -- expect to interact with mostly non-gokit services
- RPC as the messaging pattern
- Pluggable serialization and transport -- not just JSON over HTTP
- Zipkin-compatible request tracing
- more TODO
Non-goals
- Having opinions on deployment, orchestration, process supervision
- Having opinions on configuration passing -- flags vs. env vars vs. files vs. ...
- more TODO
Contributing
At this stage, we're still developing the initial drafts of all of the packages, using an RFC workflow. Before submitting major changes, please write to the mailing list to register your interest, and check the open issues and pull requests for existing discussions.
Dependency management
Users who import gokit into their package main are responsible to organize
and maintain all of their dependencies to ensure code compatibility and build
reproducibility. Gokit makes no direct use of dependency management tools like
Godep.
We will use 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 gokit's design.
Service frameworks
- Kite, a micro-service framework
- go-micro, a microservices client/server library ★
- gocircuit, dynamic cloud orchestration
- gotalk, async peer communication protocol & library
Individual components
- grpc/grpc-go, HTTP/2 based RPC
- afex/hystrix-go, client-side latency and fault tolerance library
- streadway/handy, net/http handler filters
- rubyist/circuitbreaker, circuit breaker library
- spacemonkeygo/monitor, data collection, monitoring, instrumentation, and Zipkin client library
- mattheath/phosphor, distributed system tracing
- codahale/lunk, structured logging in the style of Google's Dapper or Twitter's Zipkin
- sourcegraph/appdash, application tracing system based on Google's Dapper
- eapache/go-resiliency, resiliency patterns
- FogCreek/logging, a tagged style of logging
- Sirupsen/logrus, structured, pluggable logging for Go ★
- mailgun/vulcand, prorammatic load balancer backed by etcd
- vitess/rpcplus, package rpc + context.Context
- pivotal-golang/lager, an opinionated logging library
- inconshreveable/log15, simple, powerful logging for Go
Web frameworks
Additional reading
- Dapper, a Large-Scale Distributed Systems Tracing Infrastructure -- Google
- Your Server as a Function (PDF) -- Twitter
- Architecting for the Cloud -- Netflix
Directories
¶
| Path | Synopsis |
|---|---|
|
Package metrics provides an extensible framework to instrument your application.
|
Package metrics provides an extensible framework to instrument your application. |
|
expvar
Package expvar implements an expvar backend for package metrics.
|
Package expvar implements an expvar backend for package metrics. |
|
prometheus
Package prometheus implements a Prometheus backend for package metrics.
|
Package prometheus implements a Prometheus backend for package metrics. |
|
statsd
Package statsd implements a statsd backend for package metrics.
|
Package statsd implements a statsd backend for package metrics. |
|
teststat
Package teststat contains helper functions for statistical testing of metrics implementations.
|
Package teststat contains helper functions for statistical testing of metrics implementations. |