Skip to content
Hardcover Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions Book

ISBN: 0321200683

ISBN13: 9780321200686

Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions

(Part of the The Addison-Wesley Signature Series Series and Martin Fowler Signature Book Series)

Select Format

Select Condition ThriftBooks Help Icon


Format: Hardcover

Condition: Very Good*

*Best Available: (ex-library)

Save $46.60!
List Price $69.99
Almost Gone, Only 1 Left!

Book Overview

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...

Customer Reviews

5 ratings

SW Integration Engineering at its best

Deserves to take place in the great line up of GoF, POSA1, POSA2, EAA, Core Security Patterns (other "patterns" books omitted intentionally). 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.

The best technical book of 2004

I had been waiting for this book for several years. There are many good books on software architecture using synchronous communication, but nothing on asynchronous communication --- the typical scheme when connecting existing applications. This is surprising since the underlying products (MQ, MSMQ, WebMethods, Vitria, etc.) have been around for a while, some for more than 10 years, and the techniques have become increasingly well understood by the practitioners. There are even some books on the individual products --- several on MQ for example --- but nothing more general about how to use messaging, message routing, and message transformation to build a larger system.This is the book I had been waiting for. Furthermore the authors have avoided the usual three pitfalls of technical books: it is well organized, it well written, and it is deep treatment, not at all superficial.The book is organized into 65 patterns (in the manner of the classic _Design Patterns_). Each pattern shows one typical problem in integrating applications, and how it is solved. Each pattern gives enough implementation details so it is clear how it would work, and an example or two so it is clear how it works in practice. For example the Message Expiration pattern addresses the problem of "How can a sender of a message indicate when a message should be considered stale and thus shouldn't be processed?"The writing in this book is clear. For example "A Message Expiration is like the expiration date on a milk carton. After that date, you shouldn't drink the milk." The authors have also invented icons for each of their patterns. Their icon language allows a integration architecture to be visuallized in a way that UML does not provide.Amongst the 11 pattern-describing chapters are 3 "interludes", chapter-length examples that explain a problem, show how patterns can combined to solve it, and then provide implementations in different technologies (JMS, .Net, TIBCO, MSMQ, etc.).My only beef with this book is that it is long and dense: almost 700 pages. I bought it in late December 2003 and I am only finishing it now. But it is hard to say what should have been cut. Certainly none of the patterns are unnecessary, and the decription of each feels like about the right length. The interludes are also useful for seeing how the patterns fit together. So maybe this book just needs to be 700 pages.

Good Stuff

Enterprise Integration Patterns is part of Addison-Wesley's new Martin Fowler Signature Series, which Fowler's Patterns of Enterprise Application Architecture (PoEAA) is also a part of. I was very satisfied with PoEAA and the same can be said about Enterprise Integration Patterns. It has the potential to become a classic.The authors' writing style is a pleasure to read -- no ambiguous statements, no unnecessary babbling. The book is structured to suit both cover-to-cover reading and a "dive-in" approach for situations where you're looking for a solution to a particular problem. After an introduction to the field of enterprise integration, and a discussion of why the book concentrates on the messaging integration style in particular, the reader is given a hierarchical catalog of patterns revolving around a small set of "core" patterns. The book's coverage is in my opinion very well scoped.I must also praise the look of the book; besides the layout being familiar from prior works and the proven pattern catalog structuring, the authors have used graphics very efficiently. Not only the authors define a vocabulary for integration patterns, but they have also come up with an expressive visual language for illustrating the patterns using simple notations that can be easily drawn without CASE tools.I found only two downsides for this book. First, the title can be slightly misleading as the book focuses on messaging as an integration style and only briefly mentions alternatives such as RPC, file transfer, and shared databases. However, I don't know a single person who doesn't read the back cover before buying a book, so I wouldn't count this as a big issue. Furthermore, the reason for focusing on messaging is thoroughly argued in the book. The second downside is the code examples, which are presented using varying languages and products and seem somehow disconnected from the text.In summary, Enterprise Integration Patterns is a great book. It's worth reading and re-reading if you're working with systems integration projects or writing integration software yourself. Yet another book that makes me think, "I wish I had it back then..."

Patterns - revisited

To do justice in reviewing this book, I should depict every single pattern and give you multiple examples on how it would apply to your job as a Project Manager, Software Architect, Technical Lead or a Developer. That would be a 500-page book all by itself. In short, this is one great book. The first book to actually take a complex and ever growing topic such as MOM, Message Oriented Middleware, and give you its benefits and the best practices/patterns all in one book. The author starts by giving the reader the top reasons why messaging should be chosen for the next project:1) Remote communication2) Platform/Language Integration3) Asynchronous communication4) Variable timing5) Throttling6) Reliable Communication7) Disconnected operation8) Mediation9) Thread ManagementThe author goes into detail on each of these reasons. These reasons would convince any software architect, but the author goes even further than that and reiterates the benefits of each of these reasons and elaborates on them thru out the book. Chapter 3 of the book starts by breaking up a messaging system into its main components and briefly explaining each one:1) Message Channel2) Message3) Pipes and Filers4) Message Router5) Message Translator6) Message EndpointEach of these high level topics is then broken down and various patterns are shown for each section. Just like the GoF book, the reader can simply go the desired section and read the patterns that are associated with that "subsystem"Each section is then followed by a full-blown example, which to me is priceless. The examples are shown using the most popular middleware vendors such as TIBCO, IBM, Microsoft, Web Methods, SeeBeyond and a couple JMS vendors. The examples show the similarities and differences in implementation but clearly show how EACH pattern that was just covered in the previous section applies to the example. Having worked with many of the MOM vendors covered in this book, Chapter 7, Message Routing, is my favorite chapter. The author breaks down this topic into 14 different patterns:i) Pipes and Filersii) Message Routeriii) Content-Based routeriv) Message Filterv) Dynamic Routervi) Recipient Listvii) Splitterviii) Aggregatorix) Resequencerx) Composed Message Processorxi) Scatter-Gatherxii) Routing Slipxiii) Process Managerxiv) Message BrokerThe chances are, not many of us need to write a MOM due to the fact that there are many vendors out there that are doing that already! But one could certainly use this section for education purposes, and/or use it a checklist of "nice-to-haves" when shopping around for a MOM vendor. By reading the book, you can figure out what "features" apply to you, your application and your enterprise, and take that list and see which vendor has implemented that feature. In summary, Gregor Hohpe and Bobby Woolf have done a fantastic job depicting a very complex topic. I have made a place for this book right next to the original GoF Design Patterns book.

The best and only unbiased source for EAI material

I am working in the integration team of a big organization in Israel and we are setting up a very large scale and complex , Service Oriented, EAI project which focuses on routing and security of messages between a huge variety of systems on lots of protocols.I've been scouting the net for months looking for material on how to set up a good EAI project and what patterns, architecures, software and language environments are suitable for us. And I must say that no site compares to eai patterns. Most of the info you'll find on the net comes from some eai vendor and is all full of publicity stuff and biased opinions. what I love about eai patterns, is that it gives you all the information you need to set up a great and complex EAI router\mapper\anything without the need for any particular product. And it also shows you implementations with common eai and techologies. There is no other source which really defines the patterns and terminologies of EAI, in a global way without relation to any particular product like eai patterns. Over here at work we printed out the entire site on the mainframe printer and we use it as our guide. But now we could just get the book and have it in a much more compact manner. The only problem here is that stuff like EAI patterns and technologies get updated so fast that there is no chance the book will cover everything you need and you will probably have to look up for more on the net. But there certainly isn't a better way to get into EAI in my opinion, than buying this wonderful book. This is the EAI Bible. Great job by the authors. 5 Stars!
Copyright © 2023 Terms of Use | Privacy Policy | Do Not Sell/Share My Personal Information | Cookie Policy | Cookie Preferences | Accessibility Statement
ThriftBooks® and the ThriftBooks® logo are registered trademarks of Thrift Books Global, LLC
GoDaddy Verified and Secured