Kratos is an open-source Go microservice framework that provides full stack support for microservice related functions such as service governance, link tracing, configuration center, RPC calls, etc. It is simple yet powerful. It not only serves medium to large enterprise scenarios, but is also extremely friendly to individual developers.
Its positioning is clear: it is not the lightest or heaviest, but Kratos has done a very solid job in both "engineering practice" and "cloud native compatibility" dimensions. You can consider it as an experienced but not verbose architect, and taking action is the best practice.
Kratos provides a command-line tool called kratos to assist in the rapid generation and management of projects. Assuming you have already installed Go (recommended to use Go 1.21+), it only takes a few steps to get started
Then quickly generate a project
After startup, a complete microservice project structure is already established. It includes modules such as service entry, configuration management, gRPC interface definition, and service registration, all of which are industrial grade standards that are ready to use.
Project Structure Analysis: What exactly did it prepare for you?
Kratos' project directory may seem quite extensive at first, but it is actually well-organized and mainly includes:
API/: Used to store protobuf definition files and automatically generate gRPC and HTTP interface code.
Cmd/: Service main entrance.
Internal: The core area of actual business logic code, including service, biz, data, and other hierarchical modules.
Configs/: Configuration file directory, supports local configuration and remote configuration center.
Through this layered architecture, Kratos encourages developers to adopt a "clear division of responsibilities" coding approach to avoid code confusion and difficulty in maintenance in the later stages.
Add business logic: Step by step guide you through the process
Add the Hello World. proto file to the API/Hello World/v1 directory and define a service:
Then execute the command to generate code:
Register the service in server/grpc.go (PS: If HTTP service is required, register it in server/http.go)
In this way, a complete gRPC service and client code are ready. You only need to fill in the business logic in internal/service/wellowworld.go to run a basic request.
The advantage of Kratos is not only standardization, but also scalability
Do you want to access the registration center? Use Etcd and Consul directly.
Do you want to join link tracing? By default, OpenTelemetry is supported.
Do you want to configure dynamic distribution? Integrating Apollo and Nacos is no problem.
This also means that it is highly suitable for scenarios involving rapid iteration, cloud native deployment, and multi team collaboration.
If you're tired of the process of building wheels and stepping on potholes at the same time, Kratos is a great 'bottom layer hosting' solution. It provides a stable, reliable, and clear engineering framework that allows you to focus on the business itself.
Whether as a part of technical pre research or directly serving your core system, Kratos is a solution worth trying.