REST vs gRPC

• googleapis

  13 6,512 9.6 Starlark

  Public interface definitions of Google APIs.

  

Rich Error Model: This model enables servers to return and clients to consume additional error details expressed as one or more protobuf messages. It further specifies a standard set of error message types to cover the most common error (QuotaFailure, PreconditionFailure, BadRequest, etc). When an error occurs, the server returns the appropriate status code along with an optional error message.

• gRPC

  201 40,733 9.9 C++

  The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)

  

gRPC (Google Remote Procedure Call) is a modern open source high-performance Remote Procedure Call (RPC) framework developed by Google. Google has been using Remote Procedure Call (RPC) infrastructure called Stubby to handle communications in large-scale distributed applications since 2001. After years of internal use, Google decided to further enhance and improve the technology and launched the next generation of Stubby, which they named gRPC. It follows an RPC implementation that uses HTTP 2.0 protocol. It also uses Protocol Buffer, an open-source mechanism for serializing the data in a structured format. It describes the service interface and the payload message. Here is an example of protocol buffer message:

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project