Equally important, though, are differences in computing environments,
operating systems, and platforms, which are the major contributors to technological execution
complexities in service ecosystems. So how can these service interoperability gaps be bridged?
Consider the following design composition guiding principles that can address service
interoperability concerns:
??? Employ the loosely coupled logical design strategies, discussed previously, to alleviate
organizational interoperability concerns. Avoid bundling business and technical functionalities
that can be otherwise distributed and integrated with other business domains and
lines of business.
??? Use the network design composition style to enable proper distribution of messages and
information in interoperable environments. Similarly, the network design composition
style can bridge various lines of business and business domains across organizations.
??? Use service proxies and intermediaries to enable translation of protocols and transformation
of data and to eliminate interoperability challenges between operating systems.
??? Expand, rather than collapse, the design composition. Specifically, employ more intermediaries
and hubs, which can bridge between interoperable landscapes. Conversely, ensure
that excessive use of brokers will not hamper asset reusability.
??? Work with service clusters to define clear boundaries between service groups, each of
which should be able to maintain its technological advantages and to support different
platforms and operating systems.
Pages:
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490