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

Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley ... | Gregor Hohpe, Bobby Woolf | Excellent reference book for EAI, Messaging and Integration projects

books:

Enterprise Integra...

	Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley ... Gregor Hohpe, Bobby Woolf Addison-Wesley Professional, 2003 - 736 pages average customer review:based on 32 reviews view larger image
	for more information click here

highly recommended

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.

for more information click here

Excellent reference book for EAI, Messaging and Integration projects

This book joins my elite patterns book collection which include GoF, Core J2EE Patterns, Core Security Patterns and Refactoring to Patterns. And this book gonna be my first reference for all Integration projects.
If you are a developer or an architect then you may consider the approach of designing software projects by starting from understanding the different architectural options, development patterns and implementation strategies - these techniques makes a lot of difference rather than reading narrow focussed technology books. I been reading narrow technology specific books but learning to use PATTERNS helps a lot. After reading few chapters...I find this book definitely makes a lot of impact...and will be my one-stop guide for EAI. There is no other book which really defines the patterns and terminologies of EAI, in a global way without relation to any particular product like eai patterns.

for more information click here

Use EIP as a guide

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.

for more information click here

Excellent companion book for design and architecture

This is the second pattern book (after Core J2EE Patterns) since I started reading and using patterns. I did read about high-level GoF but I was always skeptical about ready to use inline with a programming language like Java or VB. This book is another best example yet of where patterns can really improve your application design. Applications don't miraculously integrate with one another; it needs some architecture ideas and practical experience. This book helps to demonstrate some of those ideas as patterns in action. The descriptions of the problems and their possible solutions... just helps to simplifying and resolving the design problem.

for more information click here

One sure stop solution for all integration issues

I love this book..if you want to develop /integrate different systems with message oriented technologies, then this is the book with all possible solutions

reviews: 1, 2, page 3, 4, 5, 6, 7

products you might be interested in