[DRIVERS-822] Asymmetric Routing for Remote Procedure Calls Created: 31/Jan/20  Updated: 26/Sep/22  Resolved: 26/Sep/22

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends

 Description   
Downstream Change Summary

Haven't scoped it yet but expect there to be Drivers changes.

Description of Linked Ticket

Epic Summary

Summary

Allow a client to receive a response for a request from a node different than the one it made the request to

Motivation

Sometimes we route requests to nodes that can't service those requests. Today all we can do would be to either fail those requests (and retarget + retry) or make another request from the initial node, routing the response back through that node to the client. Both of those approaches require an extra network hop that isn't strictly speaking necessary.

By routing a response directly from the initial node to the node which can service the request, a client could receive a misrouted request in 3 hops, rather than 4.

(Proposed) Client -> ineligible node -> eligible node -> client
vs.
(fail + retarget) Client -> ineligible node -> Client -> eligible node -> Client
vs.
(route request) Client -> ineligible node -> eligible node -> ineligible node -> Client

Cast of Characters

  • Product Owner:
  • Project Lead:
  • Program Manager:

Documentation

Scope Document
Technical Design Document


Generated at Thu Feb 08 08:22:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.