Usually there is a load balancer a.k.a Webserver as the gateway for your incoming REST service requests from external clients. Since a REST service request is sent via HTTP, session ids can be maintained and tracked for client requests inside the load balancer on the first hit to a PRPC node. Based on these session ids and session affinity configuration the load balancer can ensure that it routes requests to a specific PRPC node and client state can be maintained via cookies or headers.
Let me modify the question
I have 4 nodes.
I am building a REST service with the node ID passed dynamically to the URL.
So it's like 4 different URLs for 4 nodes.
When the Client hits the URL say for nodeA will the request gets route to node A.
I am assuming the URLs have different hostname:port combination. In that case, I am wandering why do you even need to pass the node ID or have a load balancer. It Looks like the clients already know which hostname:port it has to hit.