The typical SOA platform orchestrates services centrally, through pre-defined business processes, assuming that what should have already been triggered is defined in a business process. This approach doesn't account for events that occur across or outside of specific business processes. Thus complex events, in which a pattern of activities—both random and scheduled—should trigger a set of services is not accounted for in traditional SOA 1.0 architecture.
| Property | Value |
|---|
| dbpprop:abstract
|
- The typical SOA platform orchestrates services centrally, through pre-defined business processes, assuming that what should have already been triggered is defined in a business process. This approach doesn't account for events that occur across or outside of specific business processes. Thus complex events, in which a pattern of activities—both random and scheduled—should trigger a set of services is not accounted for in traditional SOA 1.0 architecture.
|
| dbpprop:reference
| |
| rdfs:comment
|
- The typical SOA platform orchestrates services centrally, through pre-defined business processes, assuming that what should have already been triggered is defined in a business process. This approach doesn't account for events that occur across or outside of specific business processes. Thus complex events, in which a pattern of activities—both random and scheduled—should trigger a set of services is not accounted for in traditional SOA 1.0 architecture.
|
| rdfs:label
| |
| skos:subject
| |
| foaf:page
| |
![[RDF Data]](/statics/sw-cube.png)
