Database Reference
In-Depth Information
The Enterprise Business Flows framework
Firstly, the presence of State Repository is a very distinctive feature, a proprietary for this
framework. It will allow all business flows to be consolidated under this technical plat-
form, deferring the transactional state while waiting for a response. It can be done by any
form of DB such as Relational, XML, or NoSQL, depending on types of messages run-
ning in these flows. The Relational type is still one of the most common; it allows you to
conduct a quick search of hibernated instances and associations with the designated Cor-
relation ID. Possible glitches, resulting in leaving orphan-hibernated records, can also be
more easily dealt with in a relational environment. The storage overhead, which is com-
mon for relational models, must be taken into consideration during the planning phase.
Also, it's important to realize a unified Enterprise Business Flow framework's state repos-
itory can present a single point of failure and/or a performance bottleneck, so proper DBA
administration, replication, and maintenance is one of the highest demands for this frame-
work.
To make business flows more manageable and centralized, another element of technical
infrastructure should be observed as a decision service is based on rules engine. We delib-
erately segregate the rules, associated with pure business logic and centralize them in one
location, thus making it possible to employ dynamic message routing and process invoca-
tion, value mapping, and data sorting processes. Of course, taking some logic away from
the compound process reduces its autonomy and also could present a single point of fail-
ure, but this calculated risk makes business flows more agile and quickly adaptable to the
shifting business conditions.
Task-orchestrated services are most commonly composed using languages based on
WS-
BPEL
specifications (Business Process Execution Language). Common requirements
(such as the implementation techniques, service models, and required functionalities) for
the GF04: EBF framework are given in the following following list of requirements:
• Implementation technique:
◦ WS-BPEL, Orchestration
• Service models:
◦ Task Orchestrated Services
• Required functionalities:
◦ Level of WS-BPEL support (versions, extensions) with full orchestration
features, which include branching, parallel processing, conditions, loop-
ing, scoping, and so on.
Search WWH ::
Custom Search