3 ms·
> Async functions, now available in many languages, solves many of the issues RPC had in its childhood. Like which problems? Transparency? Nope; the caller st
by lelanthran 4y ago
> Async functions, now available in many languages, solves many of the issues RPC had in its childhood.
Like which problems?
Transparency? Nope; the caller still needs to set up where the remote function resides, which of the multiple remote functions with that name must be executed, etc.
Latency? It actually makes it harder - you now need separate plumbing so that calls which take more than $X minutes must be considered failure.
Reliability? Not this one either - the error returned by a function will still have to be handled separately from an error returned by the network.
- Too 4y agoWell, I think a fair presumption is that the option compared with is still distributed. Network latency and disruption is always going to be an inherent part of such. The comparison was more against rpc without async. Primarily, async exposes that the call you are dealing with goes over the network. You can no longer accidentally put a blocking rpc call in the UI thread. You can easily send multiple concurrent requests without fuzz. It has built in primitives to add timeouts on any call, even chained ones, without having to rely on complicated thread-watchdogs or checkpointing.