Go microservices framework
Kratos is a lightweight Go framework for building cloud-native microservices with API-first Protobuf, unified HTTP/gRPC transport, pluggable components, and code generation.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose it for an opinionated Go microservices framework with built-in database and observability over Kratos' pluggable codegen workflow.
An opinionated GoLang framework for accelerated microservice development. Built in support for databases and observability.
Choose it for a Go microservices framework with pluggable service discovery, broker, and transport abstractions.
A Go agent harness and service framework
Choose it for built-in service governance (circuit breaking, load balancing) and ServiceComb compatibility.
a cloud native application framework for Go with rich eco-system
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose it for a high-performance Go RPC framework if you will assemble config/logging yourself.
Go RPC framework with high-performance and strong-extensibility for building micro-services.
Choose it for a lighter Go API/microservice framework with less protobuf-centric workflow.
🦅 A Go framework for the API or Microservice
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose it for a non-opinionated library-style microservices toolkit, but it is stale (no push for over 2 years).
A standard library for microservices.
These projects were analysed and named kratos among their alternatives. The relationship is not symmetric — how kratos rates them is a separate judgement, made when kratos is analysed in its own right.
calls kratos “Use Kratos when you want a similar cloud-native Go microservice framework with its own transport design and a larger CLI-driven code generation workflow.”
A cloud-native Go microservices framework with cli tool for productivity.
calls kratos “choose if you want a modular framework with explicit transport/server registration and a large ecosystem.”
An opinionated GoLang framework for accelerated microservice development. Built in support for databases and observability.
calls kratos “Full microservices framework with service discovery and RPC; choose for large distributed systems with more infrastructure needs.”
Gin is a high-performance HTTP web framework written in Go. It provides a Martini-like API but with significantly better performance—up to 40 times faster—thanks to httprouter. Gin is designed for building REST APIs, web applications, and microservices.
calls kratos “choose when you need a full cloud-native microservices framework with built-in service governance and gRPC/HTTP support instead of a minimalist HTTP framework.”
High performance, minimalist Go web framework
calls kratos “Choose when you prefer a more opinionated, cloud-native microservices framework with built-in features over go-kit's library-style approach.”
A standard library for microservices.
calls kratos “choose for a microservices-first framework with strong gRPC support and a cloud-native ecosystem.”
A powerful framework for faster, easier, and more efficient project development.
calls kratos “choose it if you want a full cloud-native application framework with HTTP/gRPC and middleware, not only high-performance RPC.”
Go RPC framework with high-performance and strong-extensibility for building micro-services.
calls kratos “when you need a cloud-native Go microservices framework without the AI-agent layer.”
A Go agent harness and service framework