Encore – the platform for building Go-based cloud backends.
What is this?
Go kit is a programming toolkit (a set of packages and best practices) for building microservices or well-structured monoliths in Go, solving common distributed-systems and architecture problems so you can focus on business logic.
Go kit is a programming toolkit (a set of packages and best practices) for building microservices or well-structured monoliths in Go, solving common distributed-systems and architecture problems so you can focus on business logic.Is this a framework or just a library of helper packages?It's described as a toolkit of composable packages rather than a rigid framework: it expects you to interact with non-Go-kit services, use RPC as the main pattern, and doesn't dictate deployment or orchestration tools.
It's described as a toolkit of composable packages rather than a rigid framework: it expects you to interact with non-Go-kit services, use RPC as the main pattern, and doesn't dictate deployment or orchestration tools.How do I add it to a Go project?Go kit is Go-modules aware, so you add it like any other module dependency; being at major version 0, it should also still work in non-modules environments.
Go kit is Go-modules aware, so you add it like any other module dependency; being at major version 0, it should also still work in non-modules environments.Do I need gRPC or a specific serialization format to use it?No specific transport or format is mandated; Go kit supports pluggable serialization and transport (not just JSON over HTTP) and is meant to operate within your existing infrastructure.
No specific transport or format is mandated; Go kit supports pluggable serialization and transport (not just JSON over HTTP) and is meant to operate within your existing infrastructure.Does it support pub/sub or other messaging patterns besides RPC?No, Go kit currently focuses only on RPC-style messaging and explicitly does not aim to support other patterns like pub/sub or CQRS, nor does it have opinions on deployment or orchestration.
No, Go kit currently focuses only on RPC-style messaging and explicitly does not aim to support other patterns like pub/sub or CQRS, nor does it have opinions on deployment or orchestration.Who is this aimed at?It's aimed at Go teams and organizations of any size building service-oriented architectures, especially those wanting JVM-ecosystem-style microservice tooling but in Go.
It's aimed at Go teams and organizations of any size building service-oriented architectures, especially those wanting JVM-ecosystem-style microservice tooling but in Go.Can code be generated automatically for Go kit services?Yes, several third-party generators exist, like sagikazarmark/protoc-gen-go-kit and metaverse/truss, that scaffold Go kit code from different starting points.
Yes, several third-party generators exist, like sagikazarmark/protoc-gen-go-kit and metaverse/truss, that scaffold Go kit code from different starting points.Why would I use Go kit instead of go-micro or gizmo?Go kit specifically targets heterogeneous SOA environments where most peer services aren't Go kit based, favors RPC as the primary pattern, and avoids opinions on deployment/orchestration, unlike more opinionated full frameworks.
Go kit specifically targets heterogeneous SOA environments where most peer services aren't Go kit based, favors RPC as the primary pattern, and avoids opinions on deployment/orchestration, unlike more opinionated full frameworks.Is Go kit still actively evolving its API?It's still at major version 0 according to the README, meaning its API isn't yet guaranteed stable.
It's still at major version 0 according to the README, meaning its API isn't yet guaranteed stable.Which topics is it in?rpc, toolkit, microservices, golang, distributed-systems, backend, go, api, server, library, developer-tools, mit
rpc, toolkit, microservices, golang, distributed-systems, backend, go, api, server, library, developer-tools, mit