DAVE'S LIFE ON HOLD

Complex System Design

Here's a scary concept, let's design a complex system. By complex I mean consists of many simple moving parts. Individually the components in the system may be trivial to implement. They may do little more than keep a running tally, pass data from point A to point B, or may transform an entire file. How this will differ from an application is that this complex system will consist of individual parts that may run as stand alone applications. It is more than Unix style design, it is a school od engineering that works for the material world as well. Any device made with off the shelf parts exhibits these basic characteristics.

Step 1.) what are the functional roles necessary to make our system work?

In general, our system wil:


This description will accurately model most systems we would want to build. The specific of each step aren't important, they only determine the scale to which we focus on any component. In general, the key problems we are trying to solve are managing a large workflow while accounting for the economic model that makes that work practical. It doesn't matter if we are gathering ore carrying it to a smelter and producing ingots, or generating personalized email spam, or rendering movies for a Hollywood film. Each of these systems will have the same basic set of requirements for the business of doing to to work.

Step 2.) What technologies can we bring to bear to address these issues:
If you notice, we can reduce the number of distinct elements through repeated application of a message driven architecture:
This design is not accidental, it is how your body works.