When business analysts model business process they tend to capture the sequence of tasks and events without trying to structure into patterns. As an example sequential workflows that usually happen between different actors are mixed with very dynamic interactions such as screen navigations with lots of back & forth or context switch actions. Event driven reactive processing is mixed with service proactive sequence handling. The risk of such mix is to face modeling limitations, and to lead implementation team to the wrong technology selection with an induced higher cost. The following picture describe the essential patterns and the corresponding technology. 

• The top layer captures the interactions between different business domains, or to take an APQC classification terminology for level 3 decomposition "processes".
• The next layer is workflow between different actor belonging to the same business subdomain .
• One layer below captures the interactions of a single human actor with the system for a particular task of the above workflow.
• The bottom layer addresses the matchmaking usually implemented in ESBs, to expose the appropriate services using adaptation or combination of existing interfaces.

 
 

To differentiate Service Oriented Architecture and Event Driven Architecture the classical gang of four work on Design Patterns  can be used as described by the following picture.