A couple of things come to mind. Sending a message to a pid does not block the sender until message is consumed. Each pid has its own mailbox. If you attempt th

A couple of things come to mind. Sending a message to a pid does not block the sender until message is consumed. Each pid has its own mailbox. If you attempt this in go (a channel per a unit comparable to a pid) it will fail pretty fast. Other than that, pretty similar from user‘s perspective. A process can reside on any node of the cluster. You don’t care about hostnames, ports… just use a node name: https://www.erlang.org/doc/reference_manual/distributed.html https://www.erlang.org/doc/reference_manual/distributed.html. You can spawn a process on another node and send anything that’s a valid Erlang term to it as if it was a local process.