Enterprise Integration Patterns Designing, Building and deploying messaging Solutions

What do you do when a new technology arrives? You learn the technology. This is exactly what Ì did. 1 studied J2EE (being from Sun Microsystems, it seemed to be the logical choice). Specifically, I focused on the EJB technology by reading the specifications (since there were no books yet). Learning the technology, however, ìs just the first step_—the real goal is to learn how to effectively apply the technology. The nice thing about platform technologies is that they constrain you to performing certain tasks. But, as far as the technology ìs concerned, you can do whatever you want and quite often get into trouble ìf you don’t do things appropriately. One thing [ve seen in the past 15 years is that there seem to be two areas that software developers obsess over: programming and designing—or more specifically, programming and designing effectively. There are great books out there that tell you the most efficient way to program certain things in Java and C#, but far fewer tell you how to design effectively. That's where this book comes in. When Deepak Alur, Dan Malks, and I wrote Core J2EE Patterns, we wanted to help J2EE developers “design” better code. The best decision we made was to use patterns as the artifact of choice. As James Baty, a Sun Distinguished Engineer, puts it, “Patterns seem to be the sweet spot of design.” 1 couldn't agree more, and luckily for us, Gregor and Bobby feel the same way. This book focuses on a hot and growing topic: integration using messaging. Not only is messaging key to integration, but it will most likely be the predominant focus in Web services for years to come. There is so much noise today in the Web services world, it's a delicate and complex endeavor just to identify the specifications and technologies to focus on. The goal remains the same, howeversoftware helps you solve a problem. Just as in the early days of J2EE and .NET, there is not a lot of design help out there yet for Web services. Would you like to use a consistent visual notation for drawing Integration solutions? Look Inside the front cover. . Do you want to harness the power of asynchronous systems without getting caught in the pittalls? See “Thinking Asynchronously” In the Introduction, Do you want to know which style of application integration is best for your purposes? See Chapter 2, Integration Styles. Do you want to learn techniques for processing messages concurrently? See Chapter 10, Competing Consumers and Message Dispatcher, Do you want to learn how you can track asynchronous messages as they llow across distributed systems? See Chapter 11, Message History and Message Store. Do you want to understand how a system designed using Integration patterns can be Implemented using Java Web services, NET message queulng, and a TIBCO-based publish-subscribe architecture? See Chapter 9, Interlude: Composed Messaging. re OER tlizing years of practical experlence, seasoned experts Gregor Hohpe and Bobby Woolf show how asynchronous messagng has proven to be the best strategy for enterprise integration success. However, building and deploying messaging solutions presents a number of problerns tor developers. Enterprise Integration Patterns provides an invaluable catalog of sixty-five patterns, with reat-world solutions that demonstrate the formidable power of messaging and help you to design effective messaging solutions for your enterprise. The authors also Include examples covering a variety of different integration technologies, such as JMS, MSMO, TIBCO ActiveEnterprise, Microsoft BizTalk, SOAP, and XSL, A case study descrlbing a bond trading system illustrates the patterns in practice, and the book offers a look at emerging standards, as well as insights into what the future of enterprise integration might hold. N This book provides a consistent vocabulary and visual notation framework to describe large-scale integration solutions across many technologies. It also explores In detail the advantages and Iimitations of asynchronous messaging architectures. The authors present practical advice on designing code that connects an application to a messaging system, and provide extensive information to help you determine when to send a message, how to route it to the proper destination, and how to monitor the health of a messaging system. If you want to know how to manage, monitor, and maintain a messaging system once it is In use, get this book, Gregor Hohpe leads the enterprise integration practice at ThoughtWorks, Inc, a specialized provider of application development and integration services. Drawing from his extensive experience designing and implementing integrat on solutions for enterprise clients, Gregor has published a number of papers and articles presenting a no-hype view on enterprise Integration, Web services, and Service-Oriented Architectures. He is a frequent speaker at technical conterences around (he world, Bobby Woolf is coauthor of The Design Patterns Smalltalk Companion (Addison-Wesley, 1998), and author of artictes in (BM DeveloperWorks, Java Developer's Joumel, and elsewhere. He has been a tutorlal presenter at OOPSLA, JavaEdge, and Smalltalk Solutions, among other conferences. .