ConnectRPC is a new protocol translation layer built into the Cosmo Router that compiles named GraphQL operations into Protocol Buffer definitions and serves them as gRPC, gRPC-Web, Connect protocol, and HTTP/JSON endpoints alongside typed SDKs (Go, TypeScript, Swift, Kotlin, etc.) and OpenAPI specs. The workflow involves
Table of contents
The Multi-Protocol Problem: Why GraphQL APIs Are Hard to Expose as REST or gRPCProtocol Choice Is a Deployment Concern, Not an Implementation ProblemNo More BFF Sprawl: Why Everything Downstream Is GeneratedIntroducing Cosmo ConnectRPCHow ConnectRPC Turns GraphQL Operations into gRPC, REST, and Typed SDKsHow the GraphQL-to-Proto Compilation Pipeline WorksWhy ConnectRPC Replaces Separate API LayersUse Cases: Partner APIs, Mobile SDKs, and Platform GovernancePerformance Characteristics of ConnectRPCDesign Principle: Protocol Translation Belongs in InfrastructureWhat's on the ConnectRPC RoadmapGet Started with ConnectRPCFrequently Asked Questions (FAQ)Sort: