gRPC [Java] Master Class: Build Modern API and Microservices - [Theory] Deadlines

The video tutorial discusses the importance of setting deadlines in GRPC to manage how long clients are willing to wait for an RPC to complete. It emphasizes the need for setting appropriate deadlines for each RPC call, considering the API's expected completion time. The server should cancel tasks if deadlines are exceeded. Deadlines are propagated across GRPC calls, ensuring all microservices in a chain are aware of the time constraints. The tutorial recommends reading a GRPC blog for further understanding.

What is the primary purpose of setting deadlines in GRPC?

• To reduce server load

• To increase the number of RPC calls

• To ensure the server works faster

• To limit the time a client waits for a response

When setting a deadline for a small API, what is a reasonable time frame?

• 5 minutes

• 100 milliseconds to 1 second

• 1 minute

• 10 seconds

What should a server do if a deadline is exceeded during an RPC call?

• Ignore the deadline and send a response later

• Continue processing until completion

• Retry the operation automatically

• Cancel the work and notify the client

How are deadlines propagated in a chain of GRPC calls?

• Deadlines are not propagated in GRPC

• Each server in the chain is aware of the deadline

• Only the last server in the chain is aware of the deadline

• Only the first server in the chain is aware of the deadline

Why is it important for all microservices in a chain to be aware of deadlines?

• To improve server response time

• To reduce the number of servers needed

• To increase the number of RPC calls

• To ensure they do not perform unnecessary work