gRPC Remote Procedure Calls
gRPC is a high-performance remote procedure call framework that uses Protocol Buffers for compact binary serialization and HTTP/2 for transport. Clients call typed methods on remote services as if they were local functions, making gRPC popular for internal microservice communication.
Technical Architecture & Deep-Dive
Originally developed at Google, gRPC generates client and server code from `.proto` contracts in many languages. Binary encoding and HTTP/2 multiplexing make it faster and smaller on the wire than JSON over HTTP/1.1.
Browsers cannot speak native gRPC directly, and many no-code platforms only understand JSON REST. Teams typically expose gRPC services to frontends through a gateway that translates to JSON, which is a natural responsibility for an edge BFF.
Key Architectural Benefits
Implement gRPC Remote Procedure Calls at the Edge
Deploy lightweight API aggregation, edge caching, and secret injection in minutes without Docker containers or complex servers.
Frequently Asked Questions
Q:Can a web frontend call gRPC directly?
Not natively. Browsers require gRPC-Web with a proxy, or a gateway that translates gRPC into JSON REST endpoints.
Related Architecture Concepts
A REST API is a web interface that exposes data as resources identified by URLs and manipulated with standard HTTP methods such as GET, POST, PUT, and DELETE. Each request is stateless and responses are usually JSON, making REST the most common style for public and internal APIs.
HTTP/2 multiplexing allows multiple requests and responses to travel concurrently over a single TCP connection as interleaved streams. Unlike HTTP/1.1, which processes one request per connection at a time, HTTP/2 removes the need for many parallel connections and reduces latency.
Microservices architecture structures an application as a collection of small, independently deployable services, each owning a single business capability and its data. Services communicate over APIs or messaging, allowing teams to build, scale, and release parts of the system separately.