Skip to content
A standard library for microservices.
Go Shell
Branch: master
Clone or download
peterbourgon Consider SRV records with port 0 as an error (#900)
* sd/dnssrv: fix Instancer method receivers

* sd/dnssrv: SRV record with port 0 is an error

* sd/dnssrv: test for SRV port zero issue

* .build.yml: update and fix
Latest commit dc489b7 Aug 12, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
auth Small fixes to fight entropy and bit-rot (#901) Aug 12, 2019
circuitbreaker Use stdlib context instead of Feb 4, 2017
cmd/kitgen fix kitgen test in the windows (#840) Feb 25, 2019
endpoint cleaned up code formatting and some doc comments per PR review Jun 18, 2018
examples Update imports for NATS (#881) Jun 6, 2019
log Add a log adapter for zap.Logger (#855) Apr 10, 2019
metrics dogstatsd: Drop metrics according to sample rate (#884) Jun 14, 2019
ratelimit Remove dependency on juju Oct 9, 2017
sd Consider SRV records with port 0 as an error (#900) Aug 12, 2019
tracing fix port assignment (#866) Apr 29, 2019
transport Update imports for NATS (#881) Jun 6, 2019
util Add backoff package and fix Consul CPU usage (#635) Apr 2, 2018
.build.yml Small fixes to fight entropy and bit-rot (#901) Aug 12, 2019
.gitignore Restore .gitignore and coverage.bash Jun 4, 2017
.travis.yml Small fixes to fight entropy and bit-rot (#901) Aug 12, 2019 CONTRIBUTING: update Aug 23, 2016
LICENSE Initial commit Feb 3, 2015 Update Gin framework homepage url (#888) Jun 24, 2019
circle.yml Fix Circle: use go1.11 (#771) Oct 1, 2018
coveralls.bash .travis.yml: run Coveralls, as Drone is gone Jul 20, 2017
docker-compose-integration.yml Add Eureka service discovery implementation Mar 23, 2017
lint lint: place here in preparation Jun 7, 2016
update_deps.bash update_deps.bash: handle detached HEAD better Sep 17, 2017

Go kit
Circle CI Travis CI status GoDoc Coverage Status Go Report Card Sourcegraph

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.


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.


  • 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


  • 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.


Please see Thank you, 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 dep, gb, glide, gvt, and govendor. 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, a microservice toolkit from The New York Times ★
  • go-micro, a microservices client/server library ★
  • gotalk, async peer communication protocol & library
  • Kite, a micro-service framework
  • gocircuit, dynamic cloud orchestration

Individual components

Web frameworks

Additional reading

Development supported by DigitalOcean.

You can’t perform that action at this time.