tRPC-Cpp Documentation

The tRPC-Cpp management service is an HTTP-based service that allows users to monitor and manage the status of their services. It provides interfaces to:

• View framework version and configuration.
• View and modify log levels.
• View server-side statistics (connection count, request count, latency, etc.).
• View framework and user-defined tvar variables.
• Collect system resource usage (CPU, memory).
• View rpcz information.
• Access Prometheus metrics.
• Customize management commands.

You can access this service via a web browser or by making manual HTTP requests (e.g., using curl).

Tvar is a multi-threaded statistics library within the tRPC-Cpp framework. It is designed to help users record and track various program states during execution.

Design Philosophy: Tvar is optimized for scenarios with frequent writes and infrequent reads. It achieves high write performance by using a thread_local mechanism, which avoids the cache bouncing issues associated with global atomic variables used in frameworks like Envoy. This approach is similar to brpc and flare, prioritizing write efficiency over read efficiency.

The tvar directory provides a collection of specialized thread-safe variables designed for high-performance telemetry and monitoring.

Design Philosophy

tvar is optimized for write-heavy scenarios. It utilizes a thread-local mechanism to maximize write performance by reducing contention between threads. As a trade-off, this design results in lower read performance compared to traditional atomic variables, making it ideal for high-frequency updates (like counters or latency tracking) where reading the aggregate value is less frequent than updating it.

The demo is organized into three main components:

• client/: Contains the client implementation (client.cc) and its configuration (trpc_cpp_fiber.yaml).
• server/: Contains the server implementation (demo_server.cc) and its configuration (trpc_cpp_fiber.yaml).
• common/: Contains the implementation of the thirdparty protocol, including codecs (demo_client_codec.cc, demo_server_codec.cc) and protocol definitions (demo_protocol.cc).

examples/features/thirdparty_protocol/
├── client
│   ├── BUILD
│   ├── client.cc
│   └── trpc_cpp_fiber.yaml
├── CMakeLists.txt
├── common
│   ├── BUILD
│   ├── demo_client_codec.cc
│   ├── demo_client_codec.h
│   ├── demo_protocol.cc
│   ├── demo_protocol.h
│   ├── demo_server_codec.cc
│   └── demo_server_codec.h
├── README.md
├── run_cmake.sh
├── run.sh
└── server
    ├── BUILD
    ├── demo_server.cc
    └── trpc_cpp_fiber.yaml

The grpc_stream example demonstrates a streaming server implemented using the tRPC framework, which transforms a standard gRPC framework server example into a tRPC-based one.

Note on Runtime Requirements: You must use the Fiber thread model for this example to function correctly.

Current Status: The streaming server is implemented, but the gRPC streaming client is still in progress.