Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley Signature Series) | 
 enlarge | Authors: Gregor Hohpe, Bobby Woolf
Publisher: Addison-Wesley Professional
Category: Book
List Price: $59.99
Buy New: $37.38
You Save: $22.61 (38%)
New (41) Used (12) from $35.95
Avg. Customer Rating:  35 reviews
Sales Rank: 26678
Media: Hardcover
Number Of Items: 1
Pages: 736
Shipping Weight (lbs): 3.3
Dimensions (in): 9.4 x 7.3 x 2
ISBN: 0321200683
Dewey Decimal Number: 005.7136
UPC: 785342200683
EAN: 9780321200686
ASIN: 0321200683
Publication Date: October 20, 2003
Availability: Usually ships in 1-2 business days
|
| Also Available In:
|
| Similar Items:
|
| Editorial Reviews:
Product Description
*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 pitfalls? 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 flow 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 queuing, and a TIBCO-based publish-subscribe architecture? See Chapter 9, Interlude: Composed Messaging. Utilizing years of practical experience, seasoned experts Gregor Hohpe and Bobby Woolf show how asynchronous messaging has proven to be the best strategy for enterprise integration success. However, building and deploying messaging solutions presents a number of problems for developers.Enterprise Integration Patterns provides an invaluable catalog of sixty-five patterns, with real-world solutions that demonstrate the formidable 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, MSMQ, TIBCO ActiveEnterprise, Microsoft BizTalk, SOAP, and XSL. A case study describing 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. 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 limitations 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. 0321200683B09122003
|
| Customer Reviews: Read 30 more reviews...
 Excellent book for validating designs at work... November 23, 2008
We had to redesign one of our really broken systems at work.
I validated our whiteboard sessions on the redesign by replacing every concept we discussed with a design pattern from this book mainly just for fun.
At the first meeting no one changed anything I drew and our main architect accepted the pattern based designed no questions asked and no changes whatsoever.
If you're architecting a data integration project at work get a cup of coffee and this book and get crackin'.
Remove much of the risk of refactoring your big apps at work.
The essential messaging pattern reference and referee for enterprise architects November 2, 2008
Deciding on the best solution for an integration problem often involves difficult discussions between architects and implementors each of whom may hold a widely differing point of view. Gregor Hohpe and Bobby Woolf have provided a marvelous reference that clearly depicts and explains the messaging pattern choices to be considered along with their respective merits. Being able to match the problem with these patterns and authoritatively illuminate and quickly settle design team discussions fully justifies having this reference near at hand.
When viewing all the forces on a pattern over the longer term, the right solution will often require a bit of additional design and implementation effort vis-a-vis the quickest (or entrenched) solution. By communicating, discussing, and applying widely-understood patterns the overall construction and maintenance costs for integration can certainly be reduced.
One real example of a much better implementation that resulted from this book was the application of the Claim Check pattern to pass a token representing a large PDF document in the message, rather than encode and embed the document itself. The book explains the pattern clearly, and the implementation was not only easier to work with (because the message payload was much smaller), but the solution has subsequently become a better fit with Enterprise Service Bus (ESB) middleware since the XML for the transaction and its metadata can be rapidly transformed without being burdened by passing the bulky PDF data within the message.
Another example was solved by using the book's detailed explanation of the Correlation Identifier pattern to facilitate the redesign of an legacy transaction message. The existing application had embedded the correlation identifier in the business message which limited the implementation to a single asynchronous message exchange. By following the book's recommendation to persist the correlation identifier outside of the business message, the application could be more readily integrated using standard messaging ESB middleware tools and became reusable in environments that required more than one messaging hop.
In both of these examples, the book served both to educate the participates on the relevant patterns and then served as a "referee" to move the discussion towards a standard and extendable solution. Without the benefit of this book as an authoritative reference, it would have been very difficult to introduce new flexible and agile messaging-based architectural solutions.
 JMS mostly October 30, 2008
The patterns in this book were illustrated mostly with JMS. There were mentions of Tibco and webMethods a few places though. It makes it sound like most of the ideas for common integration patterns started in IBM labs. My background is mostly in a commercial middleware and I recognized most of the patterns from the projects I've done the last 6 years.
The mention of BPEL in the future trends section was prophetic. It looks like all the major vendors are moving toward orchestration using BPEL.
The design patterns were fairly comprehensive but I've noticed that more are being built around SOA and WOA today. Most companies are now using SOA and REST for integrations were it makes sense to do so.
Imperative for integration projects August 29, 2008
I used this book on a recent consulting engagement and found it to be extremely useful. The authors discuss topics in depth then identify patterns in that area.
As an experienced Architect, one of the challenges I find in discussing solutions at a design level is the tendency of people to speak in implementation terms. This skews the design and makes it difficult to connect the solution with the business goals.
Hohpe & Woolfe's book provides an informative and practical language to creating flexible integration architecture.
Like the Ragu Spaghetti Sauce Commercial said ... "It's in there" April 30, 2008
I am an occasional buyer of reference works on software technologies I need to get familiar with, and I teach an evening section at a local area college in object oriented analysis and design. After reading this book, I am actively trying to construct a proposal for a new course based on its contents ... it's that good.
Quite simply, Enterprise Integration Patterns blew me away, on both a technical and pedagogical level. On the technical level, it's all here (except for "aspect" patterns like security, robustness and scalability which would each have really required another book). All the patterns necessary to successfully support asynchronous messaging between groups of remote applications ... which is the basic situation facing anyone trying to do a mashup of web services and / or construct business processes by integrating internal services via an ESB. Even the Process Manager pattern is here.
On a pedagogical level, the material is complete, very easy to read, well illustrated, and above all, well organized. Even a first look at the inside covers reveals this. The front has each of the 60+ patterns listed alphabetically, with its respective icon and 2 sentence paragraph. The back has the patterns (name and icon) clumped into 6 hierarchical "pattern buckets" (Message Endpoints, Message Construction, Message Channels, Message Routing, Message Transformation, and System Management), linked together in a single diagram, showing where the buckets fit when Application A is connected to Application B.
And on both inside covers as well as every place in the text where a pattern is mentioned (quite a bit since patterns are extensively contrasted with each other), the page number where it is defined is given with its name. This makes it very easy to use this book as a reference, because all the patterns it contains are cross-referenced in so many ways.
After an excellent introduction the first chapter explains what a pattern is, what the domain of integration patterns are, and introduces the Widget Manufacturing Company, whose problem grows as tools to handle those problems are introduced.
Bottom line ... I read this book during the two legs of a round trip flight from Chicago to San Francisco, took copious notes within the pages of the book, and walked off the 2nd plane feeling that I had seriously increased my understanding of the entire topic of how to integrate loosely coupled applications.
Not bad ... plus since I snagged an upgrade on the return flight, I can also report that two glasses of wine did not interfere in the slightest with the learning experience. The book is THAT good.
|
|
|
