What is this?
Kratos is a lightweight Go framework for building cloud-native microservices, with small, explicit APIs so your code can focus on business logic instead of plumbing.
Kratos is a lightweight Go framework for building cloud-native microservices, with small, explicit APIs so your code can focus on business logic instead of plumbing.Is this a framework I build my whole service on, or a loose set of helper libraries?It's a full framework: the Kratos CLI scaffolds a service, and you build on its explicit APIs for transport, middleware, registry, configuration, logging, encoding and code generation.
It's a full framework: the Kratos CLI scaffolds a service, and you build on its explicit APIs for transport, middleware, registry, configuration, logging, encoding and code generation.How do I get a first service up and running?Install the Kratos CLI, then create a service with it — once the generated service starts you visit a local URL to check it, and the docs cover the fuller generated service flow.
Install the Kratos CLI, then create a service with it — once the generated service starts you visit a local URL to check it, and the docs cover the fuller generated service flow.What do I need installed before I can scaffold anything?Go 1.25 or later, plus protoc and protoc-gen-go for generating code from Protobuf definitions.
Go 1.25 or later, plus protoc and protoc-gen-go for generating code from Protobuf definitions.Anything to watch out for if I'm upgrading an existing Kratos service?Moving from v2 to v3 isn't a drop-in: v3 reduces core dependencies and makes previously implicit behavior explicit, so the README says to review the migration guide before upgrading production services.
Moving from v2 to v3 isn't a drop-in: v3 reduces core dependencies and makes previously implicit behavior explicit, so the README says to review the migration guide before upgrading production services.What does Kratos handle out of the box so I don't have to wire it myself?A unified transport layer for HTTP and gRPC, composable middleware for recovery, logging, validation, tracing, metrics and auth, slog-based logging with OpenTelemetry extensions in contrib, and consistent metadata, errors, validation and OpenAPI workflows.
A unified transport layer for HTTP and gRPC, composable middleware for recovery, logging, validation, tracing, metrics and auth, slog-based logging with OpenTelemetry extensions in contrib, and consistent metadata, errors, validation and OpenAPI workflows.How does the API-first workflow look in practice?You define your API in Protobuf and Kratos generates the HTTP and gRPC code from it, so the contract drives the service implementation.
You define your API in Protobuf and Kratos generates the HTTP and gRPC code from it, so the contract drives the service implementation.What if the core lacks a registry, config store or middleware I need?Registry, configuration and encoding components are pluggable, and a contrib ecosystem adds optional integrations for registries, config stores, middleware, encodings and observability.
Registry, configuration and encoding components are pluggable, and a contrib ecosystem adds optional integrations for registries, config stores, middleware, encodings and observability.Which projects influenced Kratos's design?The README credits go-kit/kit, go-micro, google/go-cloud, go-zero and beego as design influences.
The README credits go-kit/kit, go-micro, google/go-cloud, go-zero and beego as design influences.What are similar projects?go-zero, gofr, grpc-gateway, gf, grpc-go, awesome-software-architecture, apisix, awesome-microservices
go-zero, gofr, grpc-gateway, gf, grpc-go, awesome-software-architecture, apisix, awesome-microservicesWhich topics is it in?microservices-architecture, protobuf, microservice, rpc, logging, openapi, grpc, code-generation, architecture, cloud-native, microservices, http
microservices-architecture, protobuf, microservice, rpc, logging, openapi, grpc, code-generation, architecture, cloud-native, microservices, http