An integration strategy for large enterprises

Authors

  • Dejan Risimić dejan_risimic@hsbc.ca

DOI:

https://doi.org/10.2298/YJOR0702209R

Keywords:

Hub-and-Spoke, point-to-point integration, service-oriented architecture (SOA), enterprise service bus (ESB)

Abstract

Integration is the process of enabling a communication between disparate software components. Integration has been the burning issue for large enterprises in the last twenty years, due to the fact that 70% of the development and deployment budget is spent on integrating complex and heterogeneous back-end and front-end IT systems. The need to integrate existing applications is to support newer, faster, more accurate business processes and to provide meaningful, consistent management information. Historically, integration started with the introduction of point-to-point approaches evolving into simpler hub-and spoke topologies. These topologies were combined with custom remote procedure calls, distributed object technologies and message-oriented middleware (MOM), continued with enterprise application integration (EAI) and used an application server as a primary vehicle for integration. The current phase of the evolution is service-oriented architecture (SOA) combined with an enterprise service bus (ESB). Technical aspects of the comparison between the aforementioned technologies are analyzed and presented. The result of the study is the recommended integration strategy for large enterprises.

References

Bakken, D.E., Middleware, Encyclopedia of Distributed Computing, Kluwer Academic Press, 2001.

Bieberstein, N., Bose, S., Fiammante, M., Jones, K., and Shah, R., “Service-Oriented Architecture Compass", IBM Press 2006.

Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison Wesley, 2005.

Campbell, A.T., Coulson, G., and Kounavis, M.E., “Managing complexity: middleware explained”, Distributed Computing, IT Professional, 1(5) (1999) 22-28.

Chappell, A.D., Enterprise Service Bus, O’Reilly, 2005.

Earl, T., Service-Oriented Architecture (SOA): Concepts, Technology, and Design, Prentice Hall PTR, 2004.

Fowler, M., Patterns of Enterprise Application Architecture, Addison-Wesley Professional, 2002.

Keen, M., Bishop, S., Hopkins, A., Milinski, S., Nott, C., Robinson, R., Adams, J., and Verschueren, P., “Patterns: Implementing an SOA using an Enterprise Service Bus” IBM Press 2004.

Larman, C., Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, Prentice Hall PTR, 2001.

OASIS, BPEL: Web Services Business Process Execution Language. http://www.oasisopen.org/committees/tc_home.php?wg_abbrev=wsbpel.

OASIS, Web Services Architecture http://www.w3.org/TR/ws-arch.

OASIS, Web Services Resource Framework http://www.oasisopen.org/committees/tc_home.php?wg_abbrev=wsrf.

OASIS, Web Services Security, http://www.oasisopen.org/committees/tc_home.php?wg_abbrev=wss.

OMG, UML: Unified Modeling Language, Standard Specification, http://www.uml.org.

Qusay, H.M., Middleware for Communications, Wiley, 2004.

SOAP 1.1 Specification, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.

SOAP 1.2 Specification, http://www.w3.org/2000/xp/Group/.

W3C, Web Services. http://www.w3.org/2002/ws/.

W3C, WSDL Web Services Description Language Version 2.0. Standard Specification, May 2005. http://www.w3.org/TR/wsdl20?.

WS-Policy vs SOAP 1.2 Features and Properties discussion: http://lists.w3.org/Archives/Public/www-ws-desc/2003Oct/0144.html.

Downloads

Published

2007-09-01

Issue

Section

Research Articles