A cool pattern in Erlang/Elixir might eliminate 80% boilerplate code in async/trivial distributed programming

Can you give a concrete example of when you need to do this? Messages from the same sender process will always appear in order. Messages from different sender processes don’t have a order per se, unless they were triggered by a common source process but took different routes through intermediate processes. However, I’d argue that it might be more intuitive to reduce the number of process hops.

4 Likes