From the course: Beginner's Guide to Go Protocol Buffer

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

gRPC vs. REST

gRPC vs. REST - Go Tutorial

From the course: Beginner's Guide to Go Protocol Buffer

Start my 1-month free trial Buy for my team

gRPC vs. REST

“

- [Educator] So now that we know what gRPC is, why would we use gRPC over REST? Let me share a bit about REST and then we can compare them. REST, which stands for Representational State Transfer is an architectural style for developing web services. And APIs that conform to it are called REST or RESTful APIs. That's a very brief overview of REST, but most programmers should have some experience using a REST API. So what's the difference between the two? REST is cross-platform. Uses custom message format with JSON being a popular format. Message payloads are medium to large. With high processing complexity due to text parsing. And browser support is native. gRPC is also cross-platform. Message format is defined in protocol buffers which means small message payload size and low processing complexity due to well-defined binary structure. There is also browser support, but it's done through gRPC-web. REST APIs are preferred…

Contents