This chapter dealt with the practical aspects of creating applications in Erlang. A program can consist of numerous processes, performing a worker or supervisor role. I found his approach straightforward and the modules easy to understand due to intentional programming.
I also found it interesting how a small set of behaviors abstracted out the majority of the types needed for the entire system. Client/server, event handling and finite-state machine modules covered the majority of functionality required in a parallel system. It is nice to be able to abstract this out, as it reduces the amount of complex code that needs to be tested, and helps with the fault tolerance of the system.
Between these behaviors and the supervisor abstraction, a nice API is available for the developers.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment