This older approach (sometimes called SOA 1.0) does not account for events that occur across, or outside of, specific business processes.
Thus complex events, in which a pattern of activities—both non-scheduled and scheduled—should trigger a set of services is not accounted for in traditional SOA 1.0 architecture.
This makes these enriched events visible to others, especially business analysts or marketing directors, and also allows the SOA 2.0 system to possibly automate actions to take to address some unique pattern.
Rather, each SOA 2.0 service involved in the choreography knows exactly when to execute its operations (based on defined trigger criteria) and whom to interact with.
The human intelligence processes and gathers these relationships faster than current artificial computational capability can.
It does this through a Causality Vector Engine (CVE) console application which displays events in real-time to business analysts.
Business analysts can infuse additional defining detail through an SQL query statement attached to a rule or event context.
Once the developers have coded the custom binding for both export and import, they can start to focus on the mediation flow component.
With SDO, developers do not need to be familiar with any specific API in order to access and utilize data.
Business objects model real-world entities in the architecture such as customers, accounts, loans, and travel itineraries.
If a customer cancels an order, extra manufacturing capacity could reduce the profitability of the production run.
A SOA 2.0 event could notify marketing department to create a special sales campaign that would resell the excess capacity, thereby recapturing the original profitable cost-per-unit.
Resulting business processes could also measure operational progress toward achieving goals, control operational costs by communicating just what is needed to just who needs to know, or report performance status of key processes to key decision makers.
For example, you could construct a CRM event from an "abandoned shopping cart" message (parsing the transaction, customer ID, and time), using other filters to extract the value of goods in the cart and tapping the correlation capabilities of the system to add causal indicators such as whether the commerce site was suffering performance problems.
Your CRM event might also include customer value or rank from the customer database... For another example, based on the types of independent service calls received, the SOA 2.0 platform could identify a product defect by detecting the underlying pattern of the separate complaints, then triggering an alert to engineering or production of the possible defect.
Causal Vector Engine (CVE) mechanics are implemented simply, with an expandable view of SQL constructs written in stored procedures.
The creation of additional stored procedures is accomplished through the CVE console application or by using any standard database developer's toolkit.
The results of one sample test demonstrated positive causal effect between rFIC and the dorsal anterior cingulate cortex (dACC).