trpc-go
A pluggable, high-performance RPC framework for Go, supporting multiple protocols and services per process.
What is trpc-go?
tRPC-Go is the Go language implementation of the tRPC framework, designed for building scalable and maintainable microservices. It provides a pluggable, high-performance RPC framework where all components are replaceable, allowing developers to customize implementations as needed. The framework supports multiple services in a single process, various protocols, and includes tools for code generation and mock testing.
Go developers building microservices who need a flexible, extensible RPC framework with replaceable components and robust testing capabilities. It is suitable for teams requiring high-performance services with protocol flexibility and modular architecture.
Developers choose tRPC-Go for its fully pluggable architecture, which allows customization or replacement of all components, and its built-in support for multiple protocols and services within a single process. It offers comprehensive testing tools like gomock and code generation via a command-line tool, streamlining development and maintenance.
Overview
A pluggable, high-performance RPC framework written in golang
Use Cases
Best For
- Building scalable microservices in Go with a need for customizable, replaceable components.
- Developing high-performance RPC services that require support for multiple protocols, including trpc and HTTP.
- Teams needing to run multiple services within a single process listening on different addresses.
- Projects requiring extensive mock testing capabilities using gomock and mockgen for interface testing.
- Streamlining development with code generation templates via the trpc command-line tool.
- Implementing modular architectures where third-party plugins for codec, filter, or database integrations are needed.
Not Ideal For
- Teams needing out-of-the-box, opinionated RPC frameworks with minimal configuration
- Projects where performance overhead from abstraction layers is unacceptable
- Developers unfamiliar with Go's ecosystem or RPC concepts due to the pluggable architecture's complexity
- Environments requiring extensive third-party integrations not yet covered by the tRPC ecosystem
Pros & Cons
Pros
All components are replaceable with custom implementations, as emphasized in the README, allowing deep customization for specific microservice needs.
Enables running multiple services in a single process on different addresses, streamlining deployment and resource management for microservices.
Supports any third-party protocol via codec interfaces, with built-in trpc and HTTP, reducing lock-in and easing integration with diverse systems.
Interfaces can be mocked using gomock and mockgen, facilitating comprehensive unit testing and improving code reliability.
Includes a command-line tool for generating code templates, speeding up development setup and reducing boilerplate code.
Cons
The pluggable architecture requires configuring multiple components, which can be daunting for new users and increase initial development time.
Compared to established frameworks like gRPC, the plugin ecosystem (e.g., codec, filter plugins) is smaller and may lack community-driven support.
While documentation exists, the README points to external guides, and detailed examples might be sparse, making the learning curve steeper.
Frequently Asked Questions
Related Projects
Go-zeroA cloud-native Go microservices framework with cli tool for productivity.
go-kitA standard library for microservices.
KratosYour ultimate Go microservices framework for the cloud-native era.
grpc-goThe Go language implementation of gRPC. HTTP/2 based RPC
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.