GRPC Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 40: Line 40:


Call credentials, which are attached to a call.
Call credentials, which are attached to a call.
=<tt>metadata.MD</tt>=
=HTTP REST transcoding=
gRPC services can be made accessible as REST HTTP API. This is implemented with HttpRule https://cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.HttpRule

Latest revision as of 01:00, 22 October 2024

External

Internal

TODO

Overview

gRPC is a RPC framework that uses HTTP/2 as transport protocol and Protocol Buffers as data and services definition language and serialization format.

It provides the ability to define APIs - RPC services - and generate the client and server code for the services. It also offers authentication, context propagation and documentation generation. It allows for plugging in load balancing, logging and monitoring.

An example of how to use gRPC and Protocol Buffers to implement a microservice API is available in Chapter 5. Synchronous Communication of Microservices with Go.

gRPC is part of the Cloud Native Computing Foundation (CNCF)

gRPC and Protocol Buffer Services

gRPC generates client and server code for services defined by Protocol Buffers.

See:

Protocol Buffers Services

gRPC Services Accessible over REST HTTP API

Once the protocol is defined in .proto files, HttpRule https://cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.HttpRule can be used to make the gRPC services accessible over REST HTTP.

This project translates between HTTP JSON and gRPC: https://pkg.go.dev/github.com/grpc-ecosystem/grpc-gateway

Dial Options

Security

Authentication

https://grpc.io/docs/guides/auth/

Credentials

Channel credentials, which are attached to a Channel, such as SSL credentials.

Call credentials, which are attached to a call.

metadata.MD

HTTP REST transcoding

gRPC services can be made accessible as REST HTTP API. This is implemented with HttpRule https://cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.HttpRule