Aggregation activities can help achieve
these goals by analyzing current service inventories, profiling their capabilities, and collectively
applying their functionalities towards a viable solution. Thus, the opportunity to gather service
abstractions and combine them with legacy implementations can promote an organization??™s
reusability practices and facilitate asset consolidation strategies.
To accomplish these tasks, current service inventories, which include conceptual services
and other existing operating entities, should be gathered into analysis composite structures. But
the major question would still be: Are atomic services the only ones eligible for aggregation? Can
composite services or service clusters be aggregated as well? The answer is ???Yes.??? It is imperative
to consider utilizing all service formation types offered by the asset inventories, and there should
not be restrictions on the formats chosen to aggregate. As might be expected, including composite
services in a larger composite service or cluster would yield nested formations and multiple
hierarchical layers.
Use aggregation techniques with care, and find the right asset coupling balance between
fine- and coarse-grained entities. Aggregation activities must be carefully applied to avoid tightly
coupled architecture formations. This effect can yield undesirable performance results, affect
service monitoring activities in production, and reduce service reusability across organizations.
Pages:
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261