Test1

Created By
trpc-groupa year ago
Overview

what is tRPC-Go?

tRPC-Go is a high-performance RPC framework implemented in the Go programming language, designed to facilitate the development of distributed systems.

how to use tRPC-Go?

To use tRPC-Go, follow the quick start guide provided in the documentation to set up your environment and create your first RPC service.

key features of tRPC-Go?

  • Supports multiple services within a single process, listening on various addresses.
  • Pluggable architecture allowing for custom implementations of components.
  • Mock testing capabilities using gomock and mockgen.
  • Supports any third-party protocol by implementing codec interfaces.
  • Comes with a command-line tool for generating code templates.

use cases of tRPC-Go?

  1. Building microservices that require efficient communication.
  2. Developing applications that need to support multiple protocols.
  3. Facilitating testing of distributed systems with mock services.

FAQ from tRPC-Go?

  • Is tRPC-Go suitable for production use?

Yes! tRPC-Go is designed for high performance and is suitable for production environments.

  • Can I use tRPC-Go with other programming languages?

Yes! tRPC is designed to be pluggable and can work with various languages by implementing the necessary interfaces.

  • How can I contribute to tRPC-Go?

You can contribute by checking the contribution guidelines in the repository and claiming unassigned issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
trpc-group
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago