gRPC [Golang] Master Class Build Modern API and Microservices - gRPC vs REST

The video tutorial compares REST and gRPC, highlighting their differences in terms of performance, design orientation, and code generation. REST uses HTTP 1.1 and JSON, making it slower and resource-oriented, while gRPC uses HTTP2 and Protocol Buffers, offering faster, API-oriented communication with built-in code generation. gRPC supports bidirectional and asynchronous APIs, providing more flexibility and performance, making it suitable for high-performance, scalable applications.

Which of the following HTTP verbs is NOT typically used in a REST API?

• GET

• POST

• CONNECT

• DELETE

What is a key advantage of using Protocol Buffers in gRPC over JSON in REST?

• Protocol Buffers are larger in size

• Protocol Buffers are easier to debug

• Protocol Buffers are text-based

• Protocol Buffers are faster and smaller

Which HTTP version is used by gRPC to achieve lower latency?

• HTTP/3

• HTTP/1.1

• HTTP/1.0

• HTTP/2

How does gRPC differ from REST in terms of API design?

• gRPC is resource-oriented

• gRPC does not support streaming

• gRPC is API-oriented

• gRPC uses HTTP verbs

What is a major benefit of gRPC's code generation feature?

• It allows for manual coding

• It is an optional feature

• It ensures safety and consistency

• It is not supported by Protocol Buffers

In terms of performance, how much more efficient is gRPC compared to REST according to benchmarks?

• 5 times more efficient

• 10 times more efficient

• 15 times more efficient

• 25 times more efficient

What does gRPC use to call functions directly on the server?

• HTTP verbs

• RPC mechanism

• Manual coding

• Third-party libraries