Martin Nally, a Software Developer and API designer at Apigee, explains the two primary API design models: RPC and REST. While most modern APIs use HTTP as the underlying protocol, gRPC introduces an interesting hybrid approach combining RPC with some HTTP ideas. The post delves into the similarities and differences between gRPC, REST, and OpenAPI, highlighting how each method leverages HTTP in unique ways. Nally discusses the benefits and drawbacks of each approach, making a case for the simplicity and efficiency of gRPC. He also explores how to combine the entity-oriented model with RPC for a more structured API design. Ultimately, understanding the nuances of each method can help API designers make informed choices for their applications.
https://cloud.google.com/blog/products/api-management/understanding-grpc-openapi-and-rest-and-when-to-use-them