apache/brpc

Health v2 · maintenance only

Adoption not part of the score

17621 stars · 4146 forks observed · 2026-10-07

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Apache bRPC ("better RPC") is an industrial-grade C++ RPC framework for building reliable, high-performance services and clients. It supports many protocols on a single port (HTTP/HTTPS, HTTP/2, gRPC, Redis, Memcached, Thrift, RTMP/FLV/HLS, and Baidu-internal protocols), offers sync/async/semi-sync calls, combo channels for sharded or parallel access, built-in HTTP debug services with CPU/heap/contention profilers, and an industrial-grade RAFT implementation via braft.

Use cases

• build a high-performance rpc server or client in c++
• serve multiple protocols like http, grpc, and thrift on the same port
• expose protobuf services over http/h2 with json for cross-language access
• implement a thread-safe redis, memcached, or thrift client with better performance
• build highly available distributed services with the raft consensus algorithm
• profile cpu, heap, and lock contention of a c++ backend over http
• parallelize or shard rpc calls declaratively with combo channels
• build a streaming media service with rtmp, flv, and hls

When to choose

• you need industrial-grade latency and throughput in a C++ backend such as search, storage, ads, recommendation, or machine-learning systems
• you want one server to speak many protocols (HTTP/2, gRPC, Redis, Thrift, custom) on a single port
• you need built-in observability: HTTP-accessible builtin services plus CPU, heap, and contention profilers
• you want high-performance M:N threading (bthread) and counters (bvar) for concurrent C++ services
• you are building consensus-based distributed systems and can pair it with braft

When to avoid

• your primary language is not C++ and you don't need its performance profile - gRPC, Dubbo, or similar may be simpler
• you only need simple REST APIs without multi-protocol or extreme concurrency requirements
• you want a fully managed or cloud-native service mesh ecosystem rather than a self-managed C++ library
• you need first-class Windows development support, since brpc is primarily targeted at Linux/macOS production environments

Facets

framework · maturity stable

rpc http-server http-client networking concurrency streaming microservices backend networking apis windows cpp cross-platform rpc-framework grpc protobuf raft-consensus load-balancing high-performance bthread bvar redis-client memcached-client thrift rdma rtmp-flv-hls multi-protocol apache-top-level-project m:n-threading builtin-profilers real-time linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="apache/brpc")