Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions 1st Edition
Bobby Woolf (Author) Find all the books, read about the author, and more. See search results for this author |
Gregor Hohpe (Author) Find all the books, read about the author, and more. See search results for this author |
Use the Amazon App to scan ISBNs and compare prices.
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.
Customers who viewed this item also viewed
- Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable SystemsPaperback$25.91$25.91$18.91 shippingGet it as soon as Tuesday, Feb 1
- Design Patterns: Elements of Reusable Object-Oriented SoftwareHardcover$36.82$36.82$18.20 shippingGet it as soon as Tuesday, Feb 1
Editorial Reviews
From the Back Cover
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
About the Author
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 integration 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 conferences around the world.
Bobby Woolf is coauthor of The Design Patterns Smalltalk Companion (Addison-Wesley, 1998), and author of articles in IBM DeveloperWorks, Java Developer's Journal, and elsewhere. He has been a tutorial presenter at OOPSLA, JavaEdge, and Smalltalk Solutions, among other conferences.
0321200683AB09122003
Product details
- Publisher : Addison-Wesley Professional; 1st edition (October 10, 2003)
- Language : English
- Hardcover : 736 pages
- ISBN-10 : 0321200683
- ISBN-13 : 978-0321200686
- Item Weight : 3.22 pounds
- Dimensions : 7.2 x 1.7 x 9.4 inches
- Best Sellers Rank: #93,813 in Books (See Top 100 in Books)
- #3 in Voice Recognition Software
- #33 in Object-Oriented Software Design
- #45 in Management Information Systems
- Customer Reviews:
About the authors
Discover more of the author’s books, see similar authors, read author blogs and more
Gregor Hohpe advises CTOs and technology leaders in the transformation of both their organization and technology platform. Riding the Architect Elevator from the engine room to the penthouse, he assures that corporate strategy connects with the technical implementation and vice versa.
Gregor has served as Smart Nation Fellow to the Singapore government, as technical director in Google Cloud’s Office of the CTO, and as Chief Architect at Allianz SE, where he oversaw the architecture of a global data center consolidation and deployed the first private cloud software delivery platform.
Gregor is a widely recognized thought leader on asynchronous messaging and service-oriented architectures. He co-authored the seminal book 'Enterprise Integration Patterns' (Addison-Wesley, 2004), followed by "Integration Patterns" and "Enterprise Solution Patterns", both published by Microsoft Press. He was nominated a Microsoft MVP (Most Valuable Professional) Solution Architect for his contributions to the developer community and recognized as an active member of the patterns community by the Hillside Group. In 2005, Joel Spolsky selected Gregor's article 'Starbucks Does Not Use Two-phase Commit' for his 'Best Software Writing' (APress).
Gregor speaks regularly at technical conferences around the world. He likes to cut through the hype surrounding service-oriented architectures and captures nuggets of advice in the form of design patterns that can help developers avoid costly mistakes. Find out more about his work at eaipatterns.com and architectelevator.com
Customer reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The patterns explain the different problems one typically needs to solve to do asynchronous messaging integration with legacy and modern applications.
Many of the patterns are included in commercial middleware products like webMethods, Tibco, Mulesoft, etc. Others you will need to build yourself to solve specialized problems.
The book examples are JMS and MSMQ centric, with a few Tibco examples too. The code examples are geared toward building solutions with those simple technologies rather than showing all of the middleware vendor tools. Therefore, I wouldn't read this book to learn how to code things. Read it to understand how asynchronous messaging problems should be solved, and to evaluation SOA and middleware products for features that implement these patterns.
In the last few years SOA and microservices have been the buzzwords in enterprise integration, but there are still many patterns from this book you may use because there are still many legacy apps in use that can't be modified to directly support web services, and many tasks still need to be asynchronous and decoupled.
I have done Messaging and message based integration before, but this book takes essentially what is an art form and makes a science out of it.
First it starts with 4 different styles of integration (File based, Shared Database, RPC, Messaging) and discusses them intelligently giving their advantages and disadvantages.
Then it gets in to the major aspects/ pieces of Message based integration (Message, Channel, Routing, Transformation, End Points, System Management etc). It again discusses them as patterns and develops a good vocabulary of the messaging domain.
Then comes the meat where for each aspect of Messaging, it gives about 8 to 15 specific patterns, names them, shows their pros and cons, gives the trade off and intelligently discusses their usage. As part of the examples it draws example from JMS/ TIBCO/ MSMQ etc. Priceless.
What I loved about this book is how it makes you rethink everything you may have been doing before in software architecture/ integration using technologies such as Web Services, JMS, J2EE etc.
For example, many would not have fully groked MDBs as "event driven", "competing", "transactional" message consumers, that are suited for "Point to Point" integration. Yes I know every body uses them but do you really understand the implications for transaction scope and threading? . Or Polling message consumers have their advantages ?
Good discussion on relate standards and technologies included (Web Services, Axis Implementation, WS-*, SOAP etc)
Buy this guys and may be enterprise integration would be less messy.
Chapter 2 takes the reader through the integration efforts of a fictional enterprise to demonstrate some of the patterns in action. The descriptions of the problems and their possible solutions... just make sense. You can really see the benefit that these patterns provide to simplifying, organizing and clarifying the situation.
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.
Top reviews from other countries
The book is very accessible, written and illustrated clearly and assuming very little initial knowledge. However it will also provide value to the experienced messaging developer, formalising his or her knowledge and suggesting new ways of using messaging to solve different problems. I particularly like the way that Hohpe and Woolfe lay out each pattern using language and visual styles to naturally delimit the sections of the pattern, rather than using lots of sub-headings. This increases the readability significantly.
Several books on patterns talk about a "pattern language", the idea of describing a complete design in terms of named patterns for the architectural form of each component. However this is one of the first books I have read which really adopt this idea - the authors have created a new visual language, which they first use to describe basic patterns in terms of basic message constructs, and then describe more complex patterns and solutions using the icons for the intermediate patterns. Best of all you can download a Visio stencil from the website and start using and extending the pattern language yourself.
The book is remarkably technology-agnostic, providing many examples in both .NET and Java forms, and with a fair sprinkling of other technologies, for example using proprietary EAI tools such as Tibco. I have certainly seen and used some of these patterns in older file-based integration schemes, and I suspect many of them work for Web Services too. As such the book has a much better claim to be a true "patterns" book than one wedded solely to a single technology base.
Each group of pattern descriptions is followed by a detailed "practical example" section which shows how one or more messaging technologies can implement the preceding patterns to solve real problems. There aren't any real "antipatterns" in the book, but the book is realistic about when a given technology or pattern should not be used, which is just as valuable.
If I have a complaint it's a minor one, that the book is too long. Including the multiple introductions, it runs to over 700 pages. Dipping in and out my read through has taken many months. Like many patterns books, in an attempt to keep each description self-contained you find by half-way through that some basic things are being repeated regularly. A more "normalised" structure might have been better. Also, although most of the book is very readable, a couple of chapters by "guest" authors, including the final one on Web Service standards, take a more academic tone.
That said, this is an excellent book, which can be read from cover to cover, or stands as a general-purpose reference, and I strongly recommend it.
I came to this book while working on a project that required two disparate databases to be synchronised. The initial painful experiment of polling for changes was thrown out and we moved to an efficient event-based system using a message queue. Using this book allowed us to side step many issues (such as mutating table errors) and also provided us with a syntactically reference which created a common vocabulary. Such a simple thing but it saved hours of time as we were all aware of what each other in a large team mean when we discussed such things as Message Channels, Idempotent Receivers, Content Enricher and Even-Driven Consumers.
As a tip, I would recommend that all Java developers download Apache Camel which was designed around these patterns. This allows you to see first hand how and why these patterns are so useful and really compliment the book.
I've just purchased the December 2008 reprint of this book and frankly it's as valid today as it was when it came out. Messaging as an implementation style may not be quite as popular, what with the rise of data/compute grids etc, but problems and patterns are largely timeless. As a handbook for enterprise integration I haven't seen a better guide. I give it four stars only because I'd like to see a new edition that deals with integration around contemporary approaches like cloud and mega-scale patterns like map/reduce.
I paid just under thirty quid, which is slightly above average for a tech book but worth every penny when you think a few dodgy design decisions would cost your company vastly more to fix.