Hacker News Reader

Comment by andrekandre | Hacker News Reader

  > To handle this correctly you need your RPC framework to accurately communicate retryable vs non-retryable failures to clients.

basically enumerate your errors, and depending on the type, retry or just return/forward that same "dont retry this" error?

View on HN

Pretty much, but ideally it should be transparent to your app developers. App developer writes `rpc.doThing(...)` on one side, and an implementation on the other, and the infrastructure -- the RPC framework or the service mesh or whatever -- transparently handles when/whether to retry and where to route retries.

Reply on news.ycombinator.com