SYSTEM Cited by 1 source
connect-go¶
What it is¶
connect-go is a Go RPC framework that is wire-compatible with gRPC but supports additional transports and encodings beyond gRPC's standard HTTP/2 + protobuf shape — notably gRPC-Web (browser-native) and Connect's own simpler HTTP protocol. It's the RPC framework PlanetScale uses on the server side of its public HTTP API (Source: sources/2026-04-21-planetscale-faster-mysql-with-http3).
Why it shows up on this wiki¶
Canonical wiki citation comes via the ability to use HTTP/3 as a transport. From the Robenolt post: "Our new APIs aren't just gRPC. Specifically, on our end, we use connect-go, which is gRPC-compatible and gives us a bunch of other features. One of these features is the ability to potentially use HTTP/3 as a transport." This is the hook that lets PlanetScale's experimental Go client speak HTTP/3 to the same gRPC-compatible service endpoint the production JavaScript driver uses.
Architectural properties¶
- gRPC-compatible wire format — existing gRPC clients can still consume a connect-go service.
- Transport-flexible — works over HTTP/1.1, HTTP/2, or HTTP/3 (the latter via QUIC libraries like quic-go).
- Protobuf-encoded payloads on the wire.
- Go-native — designed for ergonomics in Go server code;
pair of
connect-gofor Go +@bufbuild/connect-webfor browsers.
Stub¶
Minimum viable page. Extend with first-party connect-go internals (streaming, interceptors, error model) when a post ingested discloses them.
Seen in¶
- sources/2026-04-21-planetscale-faster-mysql-with-http3 — disclosed as the server-side RPC framework behind the PlanetScale HTTP API; the HTTP/3 transport hook in connect-go is what enables the experimental Go-client HTTP/3 benchmark.