Database Reference
In-Depth Information
As a result, the layers of the Service Inventory are established for the task and en-
tity services.
• Design new, full-scale, functional compositions to minimize the creeping of busi-
ness logic, that is, reduce the number of compositions for maintenance and re-
usability purposes. This is the classic top-down approach .
A top-down approach means to devise a complete analysis upfront. It does not
just take a lot of time, but considering a dispersed GU, it requires deep and pre-
cise knowledge of the entire business operation everywhere, not to mention a sub-
stantial budget. In general, it is too late to conduct a top-down analysis at this
stage, although the analysis itself is a positive practice.
• Use SCAs to implement compositions in a static BPEL way. Dynamic Service/
Endpoint invocations with lookups, avoiding the creation of BPEL flows, are
more visible when it comes to inexperienced developers.
The Utility Services layer in the Service Repository is deliberately neglected for
the purpose of simplification. In fact, it can potentially lead to the implementation
of hybrid services. In this case, reliability (Objective 1; the first objective from
the objectives table at the beginning of this chapter) is reduced.
If vendors' SOA knowledge is deliberately not considered very high (for the man/
hour cost reasons), it will broaden the choice of vendors; however, this potentially
invites inexperienced solution providers and affects reliability.
In general, processes will be identical to minor alterations and developed using
the copy and paste approach. Maintainability (Objective 3) will be severely affec-
ted. With no common Utility components as the single point of failure, reliability
can be high. However, without design time discovery, after several implementa-
tion laps, it will be virtually impossible to maintain the desired level of reusability
(Objective 2).
Reliability (Objective 1) can vary by process, depending on the complexity of the
orchestration logic. The more complex the "if-else" logic used, the more prone to
errors the process will be. As a workaround solution, SCA mediators with static
dispatching logic can be implemented. Math for mediator filters/branches can be
the same as that for the number of processes.
• Service Endpoint handling in ESB is similar to the SCA solution. The number of
services will equal the number of channels multiplied by the number of affiliates.
Goals will be affected in a similar way.
Search WWH ::




Custom Search