Your Garage botysf16 Amazon Fashion Learn more Discover it Melvins Fire TV Stick Sun Care Patriotic Picks Shop-by-Room Amazon Cash Back Offer WienerDog WienerDog WienerDog  Amazon Echo  Echo Dot  Amazon Tap  Echo Dot  Amazon Tap  Amazon Echo Introducing new colors All-New Kindle Oasis Segway miniPro

Customer Reviews

4.8 out of 5 stars68
Your rating(Clear)Rate this item

There was a problem filtering reviews right now. Please try again later.

on October 28, 2003
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 communication
2) Platform/Language Integration
3) Asynchronous communication
4) Variable timing
5) Throttling
6) Reliable Communication
7) Disconnected operation
8) Mediation
9) Thread Management
The 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 Channel
2) Message
3) Pipes and Filers
4) Message Router
5) Message Translator
6) Message Endpoint
Each 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 Filers
ii) Message Router
iii) Content-Based router
iv) Message Filter
v) Dynamic Router
vi) Recipient List
vii) Splitter
viii) Aggregator
ix) Resequencer
x) Composed Message Processor
xi) Scatter-Gather
xii) Routing Slip
xiii) Process Manager
xiv) Message Broker
The 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.
0Comment|111 people found this helpful. Was this review helpful to you?YesNoReport abuse
on July 4, 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.
0Comment|43 people found this helpful. Was this review helpful to you?YesNoReport abuse
on March 29, 2004
This a book about enterprise integration solutions, authors claim that they are technology neutral, it is true. In the examples and implementations, they chose 3 most popular messaging frameworks to illustrate the patterns. However, they are pretty biased toward messaging as the "better" solution to enterprise integration strategy. It may have a lot of edges over the other approaches, sometimes it is just easy to use a simple wrapper/facade to do the integration. But I guess authors really intend to push their messaging solutions as the subtitle indicates.
Having said that, this is an excellent book of message pattern language, which I believe is the first one introducing the interesting topic. The books touches from the architectural patterns, e.g., messaging bus, pipe and filters, to common design patterns, e.g., publish/subscribe, request/reply, to some patterns that most MOMs provide as integrated solutions, e.g., durable subscriber, message filter, message expiration etc. With all these patterns at hand, a system architect would be able to craft a messaging pattern-oriented enterprise integration architecture by applying the appropriate patterns compositely.
The book would be better if authors describe some patterns implementation in more detail. E.g., it would be interesting to see how the message expiration is implemented, does the message contain a timer or the message channel monitor each individual message from start up? How does the channel interact with the message and check the expiry? Guaranteed delivery is another example. I know most of these implementation details only interest MOM developers, whereas pattern users are only interested in how and when to apply the patterns, but now that the book is about patterns themselves, implementation details would be appreciated.
Since all the patterns introduced in the book form a messaging pattern language, knowing each pattern's strength and limitation under the context, scope and different forces, and how it interacts with other patterns to form a bigger(composite) pattern are essential to grasp the pattern language. A collaboration diagram to show each pattern's transition/migration/composition to each other would be helpful.
0Comment|27 people found this helpful. Was this review helpful to you?YesNoReport abuse
on December 21, 2003
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..."
0Comment|14 people found this helpful. Was this review helpful to you?YesNoReport abuse
on December 19, 2005
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.
0Comment|11 people found this helpful. Was this review helpful to you?YesNoReport abuse
on April 29, 2009
This review is for the kindle version of the book.

So far, the book has been an excellent discussion on integration patterns in general and messaging in particular. I would likely give the text version of the book a 4 or a 5 on content.

Unfortunately, the Kindle version suffers from some formatting flaws which bring the rating down a bit.

- The table of contents does not link directly to it's contents.
- Sidebar panels and examples (of which there are many) are almost unreadable because they are formatted in a such a way that the text flows off the page. One must select the text with the thumbstick and scroll back and forth to read it.

Hopefully, Addison-Wesley will correct the errors.
44 comments|29 people found this helpful. Was this review helpful to you?YesNoReport abuse
on October 26, 2003
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!
0Comment|8 people found this helpful. Was this review helpful to you?YesNoReport abuse
on January 2, 2006
This book was exactly what I was looking for to help me scope an integration solution. For me, patterns help solve, better understand, and therefore, better communicate the technical issues of a complex software project; an enterprise integration project is complex. I was better able to communicate and estimate the scope of the project using EIPs as a GUIDE. The pattern icons (and Viso stencils found on the links page of the web site) saved me tremendous amounts time and narrative in the design documents.

Patterns do not, in themselves, promote a technology. Some of the reviews have been critical/complementary about the examples provided in the book that refer/don't refer to a specific technology. If your goal for integration is to provide a "loosely coupled" solution, this book will first GUIDE you to a message based solution.

After I gathered the functional requirements (use cases) for my integration project, I used this book to GUIDE me through the design process. Often during the design (and later in development) phase of any project, I struggle with a solution to a difficult technical problem. That is where design patterns help me. Has someone already solved this problem? Ah, yes and look how they solved it, of course that is the way you'd do it! Here is the design pattern and it's brilliant. Patterns are technologically agnostic.

We were then able to use the design, based on EIPs, to GUIDE us through choosing the integration technologies that best allowed us to implement these patterns.
0Comment|7 people found this helpful. Was this review helpful to you?YesNoReport abuse
on January 23, 2014
I've been a s/w architect for years so ... I've encountered most of these integration patterns. As I went through patterns that I haven't used, I kept the same question in my head: how is this better than if I just did it without a pattern (this is the same question I keep applying to frameworks and tools such as ESBs and business process orchestration languages like BPEL). With this, I found the authors thought along the same lines and were able to provide those answers without my having to think about the issue of not using the pattern. You have to know what the alternatives are that the pattern is trying to resolve and just why the alternatives are a problem -- and this book delivers on that. Note: I found it was helpful to keep in mind that these are application integration patterns: patterns for integrating applications as opposed to patterns for building an enterprise application.
0Comment|4 people found this helpful. Was this review helpful to you?YesNoReport abuse
on November 6, 2003
I highly recommend this book because it offers solutions for many of the problems in enterprise software integration. I was able to participate in the on-line group reviewing the patterns. The authors were humble in receiving feedback and persistent in their desire to identify useful patterns with meaningful examples.
I am using these patterns at my present company designing in-house middleware solutions. The book is not just patterns, but a Pattern Language of Messaging for anyone needing to work in middleware. This will be a great reference for years to come!
0Comment|6 people found this helpful. Was this review helpful to you?YesNoReport abuse