In contrast to the previous chapters that deal with implementing fault-tolerant systems, this chapter of the Armstrong's thesis has more to do with OTP-specific implementation.
The concept of "behavior" is new to me. I think it is rather unusual for a programming environment to offer such a high-level support. The idea seems cool that there are common programming patterns ready for one to leverage and to piece them together into an application. On the other hand, it is hard to judge on how customizable these stock patterns really are just by reading through the examples, but it does seems promising.
What's also cool about the code structure Armstrong presents here is that by separating out the application-specific code into a module, the bulk of the patterns are generic and reusable. This style can also be leveraged in other environments to construct a more reusable infrastructure.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment