Want a NOOK? Explore Now
Large IT organizations increasingly face the challenge of integrating various web services, applications, and other technologies into a single network. The solution to finding a meaningful large-scale architecture that is capable of spanning a global enterprise appears to have been met in ESB, or Enterprise Service Bus. Rather than conform to the hub-and-spoke architecture of traditional enterprise application integration products, ESB provides a highly distributed approach to integration, with unique capabilities that allow individual departments or business units to build out their integration projects in incremental, digestible chunks, maintaining their own local control and autonomy, while still being able to connect together each integration project into a larger, more global integration fabric, or grid.
Enterprise Service Bus offers a thorough introduction and overview for systems architects, system integrators, technical project leads, and CTO/CIO level managers who need to understand, assess, and evaluate this new approach. Written by Dave Chappell, one of the best known and authoritative voices in the field of enterprise middleware and standards-based integration, the book drills down into the technical details of the major components of ESB, showing how it can utilize an event-driven SOA to bring a variety of enterprise applications and services built on J2EE, .NET, C/C++, and other legacy environments into the reach of the everyday IT professional.
With Enterprise Service Bus, readers become well versed in the problems faced by IT organizations today, gaining an understanding of how current technology deficiencies impact business issues. Through the study of real-world use cases and integration patterns drawn from several industries using ESB—including Telcos, financial services, retail, B2B exchanges, energy, manufacturing, and more—the book clearly and coherently outlines the benefits of moving toward this integration strategy. The book also compares ESB to other integration architectures, contrasting their inherent strengths and limitations.
If you are charged with understanding, assessing, or implementing an integration architecture, Enterprise Service Bus will provide the straightforward information you need to draw your conclusions about this important disruptive technology.
ForewordPrefaceChapter 1: Introduction to the Enterprise Service BusChapter 2: The State of IntegrationChapter 3: Necessity Is the Mother of InventionChapter 4: XML: The Foundation for Business Data IntegrationChapter 5: Message Oriented Middleware (MOM)Chapter 6: Service Containers and Abstract EndpointsChapter 7: ESB Service Invocations, Routing, and SOAChapter 8: Protocols, Messaging, Custom Adapters, and ServicesChapter 9: Batch Transfer LatencyChapter 10: Java Components in an ESBChapter 11: ESB Integration Patterns and Recurring Design SolutionsChapter 12: ESB and the Evolution of Web Services Appendix A: Appendix: List of ESB VendorsChapter 13: BibliographyColophon
Anonymous
Posted July 3, 2004
Chappell describes a highly promising but still speculative technology for connecting together enterprise-wide computations. It can also potentially be used to span different companies. Some of you may groan. Haven't we heard this already, several times? Remember the toutings of CORBA, Java's RMI, JMX, JMS, and the nascent Web Services? Well, ESB draws upon often bitter lessons learnt with these earlier endeavours. CORBA was widely found to be too complex. RMI works only for tightly coupled systems, which do not scale well. So that became one reason for JMS, because it enabled loose coupling. But JMS is too low level. Web Services may indeed be promising, but face a danger of overspecifying a standard before enough practical experience is garnered. ESB tries to subsume the best ideas from the above, and from other efforts. It promises loose coupling and an incremental rollout, amongst other things. The incremental ability may be key to getting a small scale project approved and implemented, due to its minimal investment. You could think of ESB as taking the ideas of the JMX management console a step further. Plus, ESB can use JMX as a subsidiary technology. Chappell also offers nice visual component schematics that could be used to represent and perhaps even assemble an ESB network. If this indeed is possible, it would be tremendous. Akin to the 1980s, when MicroSim offered a graphical version of Spice, with electronic parts availabled from a menu.
1 out of 1 people found this review helpful.
Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Overview
Large IT organizations increasingly face the challenge of integrating various web services, applications, and other technologies into a single network. The solution to finding a meaningful large-scale architecture that is capable of spanning a global enterprise appears to have been met in ESB, or Enterprise Service Bus. Rather than conform to the hub-and-spoke architecture of traditional enterprise application integration products, ESB provides a highly distributed approach to integration, with unique ...