Erlang

Erlang June 19, 2024 by Marcos Benevides

:ID: de7d0e94-618f-4982-b3e5-8806d88cad5d

Resources:

Etudes for Erlang
(Laurent 2017): Notes from [BROKEN LINK: f5e7bb90-792d-406a-8c40-2b072db63a13]
(Armstrong 2013): Notes from [BROKEN LINK: 1daea4ea-40bc-406d-8d03-906c7f9ec343]
(Cesarini and Vinoski 2016): Notes from [BROKEN LINK: ffac18bd-4e44-4a7b-8a3a-a85552c9b076]
Joe Armstrong’s PHD thesis

The Erlang view of the world can be summarized in the following statments (Armstrong 2003):

Everything is a process.
Processes are strongly isolated.
Process creation and destruction is a lightweight operation.
Message passing is the only way for processes to interact.
Processes have unique names.
If you know the name of a process you can send it a message.
Error handling is non-local.
Processes do what they are supposed to do or fail.

References

Armstrong, Joe. 2003. “Making Reliable Distributed Systems in the Presence of Software Errors.”

———. 2013. “Programming Erlang: Software for a Concurrent World.”

Cesarini, Francesco, and Steve Vinoski. 2016. Designing for Scalability with Erlang/Otp: Implement Robust, Fault-Tolerant Systems. O’Reilly Media, Inc.

Laurent, Simon St. 2017. Introducing Erlang: Getting Started in Functional Programming. O’Reilly Media, Inc.

Erlang June 19, 2024 by Marcos Benevides

References

Links to this note