Repository files navigation

Go kit is aprogramming toolkit for building microservices(or elegant monoliths) in Go. We solve common problems in distributedsystems and application architecture so you can focus on deliveringbusiness value.

• Website:gokit.io
• Mailing list:go-kit
• Slack:gophers.slack.com#go-kit (invite)

Encore – the platform for building Go-based cloud backends.

Clickhere or Sponsor, above, for more information on sponsorship.

Go has emerged as the language of the server, but it remains underrepresentedin so-called "modern enterprise" companies like Facebook, Twitter, Netflix, andSoundCloud. Many of these organizations have turned to JVM-based stacks fortheir business logic, owing in large part to libraries and ecosystems thatdirectly support their microservice architectures.

To reach its next level of success, Go needs more than simple primitives andidioms. It needs a comprehensive toolkit, for coherent distributed programmingin the large. Go kit is a set of packages and best practices, which provide acomprehensive, robust, and trustable way of building microservices fororganizations of any size.

For more details, seethe website,the motivating blog post andthe video of the talk.See also theGo 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 seeCONTRIBUTING.md.Thank you,contributors!

Go kit ismodules aware, and weencourage users to use the standard modules tooling. But Go kit is at majorversion 0, so it should be compatible with non-modules environments.

There are several third-party tools that can generate Go kit code based ondifferent starting assumptions.

• RecoLabs/microgen
• GrantZheng/kit
• kujtimiihoxha/kit (unmaintained)
• nytimes/marvin
• sagikazarmark/mga
• sagikazarmark/protoc-gen-go-kit
• metaverse/truss
• goadesign/goakit

Projects with a ★ have had particular influence on Go kit's design (or vice-versa).

• 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

• 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

• Gorilla
• Gin
• Negroni
• Goji
• Martini
• Beego
• Revel (consideredharmful)
• GoBuffalo

• Architecting for the Cloud — Netflix
• Dapper, a Large-Scale Distributed Systems Tracing Infrastructure — Google
• Your Server as a Function (PDF) — Twitter