gRPC [Golang] 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 setting deadlines for every RPC call to provide an upper bound on execution time. The tutorial explains how to set deadlines based on API size and the server's role in canceling tasks if deadlines are exceeded. It also covers the propagation of deadlines across chained gRPC calls and recommends further reading on the gRPC blog.

What is the primary purpose of setting deadlines in gRPC?

• To ensure the server works faster

• To reduce server load

• To limit the time a client waits for a response

• To increase the number of RPC calls

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

• 100 milliseconds to 1 second

• 1 minute

• 10 seconds

• 5 minutes

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

• Continue processing until completion

• Ignore the deadline and send a response

• Cancel the work and notify the client

• Retry the operation automatically

How are deadlines propagated in a chain of gRPC calls?

• Deadlines are reset at each server

• Each server in the chain is aware of the original deadline

• They are not propagated

• Only the first server in the chain is aware

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

• To allow for more flexible deadlines

• To increase the speed of the entire chain

• To prevent unnecessary work if the deadline is exceeded

• To ensure they all complete tasks simultaneously