2 ms·
But all the assumptions you make about reliability in a single box go right out the window when you start building a distributed app. The point is that you can'
by cageface 15y ago
But all the assumptions you make about reliability in a single box go right out the window when you start building a distributed app. The point is that you can't rely on simple shared memory mechanisms anymore. All those pretty parallel algorithms go straight in the bin. This is why Erlang looks nothing like Haskell.
And if you have to endure the pain of writing a distributed app, why would you layer another level of concurrent complexity underneath it?
- nupark2 15y agoLocal concurrency and shared memory can be used to improve performance of operations that may be distributed; assuming proper implementations, a shared memory mailbox will always be cheaper than forcing multiple data copies of network/pipe based messaging, even if the API for both transports is identical.