The article doesn't use the OTP libraries in Erlang unfortunately. This means that you have a view of low-level Erlang message passing, but most - proper - Erla

The article doesn't use the OTP libraries in Erlang unfortunately. This means that you have a view of low-level Erlang message passing, but most - proper - Erlang programs will process messaging at a much higher abstraction. The most important omission in the example is to monitor processes. If an error occurs in another process while it is processing for a client should have the client knowing about that problem. Otherwise you are facing either a dead-lock situation or a timeout condition which you have to wait until triggers. In other words: Real Erlang programming is not like this.