4 ms·

Joe Armstrong (the creator of Erlang) said the same thing back in 2008. > The fundamental problem with taking a remote operation and wrapping it up so that it

by mietek 4y ago

Joe Armstrong (the creator of Erlang) said the same thing back in 2008. > The fundamental problem with taking a remote operation and wrapping it up so that it looks like a local operation is that the failure modes of local and remote operations are completely different. > If that's not bad enough, the performance aspects are also completely different. A local operation that takes a few microseconds, when performed through an RPC, can suddenly take milliseconds. http://armstrongonsoftware.blogspot.com/2008/05/road-we-didnt-go-down.html http://armstrongonsoftware.blogspot.com/2008/05/road-we-didn...

valenterry 4y ago
Thx, always feels good to be confirmed by what someone write ~15 years ago. I think he's right.
- mietek 4y ago
  A comment under Joe’s post points out that this has been understood at least since 1994. > We argue that objects that interact in a distributed system need to be dealt with in ways that are intrinsically different from objects that interact in a single address space. These differences are required because distributed systems require that the programmer be aware of latency, have a different model of memory access, and take into account issues of concurrency and partial failure. > We look at a number of distributed systems that have attempted to paper over the distinction between local and remote objects, and show that such systems fail to support basic requirements of robustness and reliability. https://web.archive.org/web/20030310070307/http://research.sun.com/techrep/1994/smli_tr-94-29.pdf https://web.archive.org/web/20030310070307/http://research.s...
twic 4y ago
We can go further - the very first of Peter Deutsch's Fallacies of Distributed Computing, written in 1994, is [1]: > The network is reliable. [1] https://www.computing.dcu.ie/~ray/teaching/CA485/notes/fallacies.pdf https://www.computing.dcu.ie/~ray/teaching/CA485/notes/falla...

by mietek 4y ago

valenterry 4y ago

Thx, always feels good to be confirmed by what someone write ~15 years ago. I think he's right.

mietek 4y ago
A comment under Joe’s post points out that this has been understood at least since 1994. > We argue that objects that interact in a distributed system need to be dealt with in ways that are intrinsically different from objects that interact in a single address space. These differences are required because distributed systems require that the programmer be aware of latency, have a different model of memory access, and take into account issues of concurrency and partial failure. > We look at a number of distributed systems that have attempted to paper over the distinction between local and remote objects, and show that such systems fail to support basic requirements of robustness and reliability. https://web.archive.org/web/20030310070307/http://research.sun.com/techrep/1994/smli_tr-94-29.pdf https://web.archive.org/web/20030310070307/http://research.s...

twic 4y ago

We can go further - the very first of Peter Deutsch's Fallacies of Distributed Computing, written in 1994, is [1]: > The network is reliable. [1] https://www.computing.dcu.ie/~ray/teaching/CA485/notes/fallacies.pdf https://www.computing.dcu.ie/~ray/teaching/CA485/notes/falla...