|HOME PATTERNS RAMBLINGS ARTICLES TALKS DOWNLOAD BOOKS CONTACT|
Patterns and Best Practices for Enterprise Integration
This site is dedicated to making the design and implementation of integration solutions easier. The solutions described here are relevant for a variety of integration tools and platforms such as IBM WebSphere MQ, TIBCO, Vitria, WebMethods (Software AG), or Microsoft BizTalk, messaging systems such as JMS, WCF, Rabbit MQ, or MSMQ, ESB's such as Apache Camel, Mule, WSO2, Oracle Service Bus, Open ESB, SonicMQ, Fiorano or Fuse ServiceMix plus other SOA and Web-service solutions.
All content on this site is original and is maintained by Gregor Hohpe. I have been building integration solutions for large clients for many years and enjoy sharing my findings with the community. You can find the most recent content in my Ramblings. Please contact me if you have suggestions or feedback.
Enterprise Integration Patterns
Enterprise integration remains more difficult than it should be. While integrating systems is inherently complex, one major stumbling blocks used to be the lack of a common vocabulary and body of knowledge for asynchronous messaging architectures. Under the guidance of Martin Fowler and Kyle Brown, Bobby Woolf and I filled this gap with a pattern language consisting of 65 integration patterns, which establish a technology-independent vocabulary and a visual notation to design and document integration solutions.
The full text for each pattern is available in the book Enterprise Integration Patterns, which also explores the advantages and "gotchas" of asynchronous messaging architectures. You can learn how to connect applications to a messaging system, how to route messages to the proper destination, and how to monitor the health of a messaging system. The patterns in the book come to life with examples implemented in different messaging technologies, such as SOAP, JMS, MSMQ, .NET, TIBCO and other EAI Tools. See for yourself by Downloading a sample chapter!
"The core language of EAI, defined in the book Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf, is also the core language of defining ESB flows and orchestrations, as seen in the ESB's developer tooling."
"If you are involved with the operation or development of an enterprise application, there will doubtless come a time when you will need to integrate your application with another using the emerging preferred approach of messaging. When that time comes, this book will be your most valuable reference."
--Randy Stafford, Oracle [More Testimonials]
New Book: Enterprise Transformation
As enterprise integration remains a relevant topic some 13 years after Enterprise Integration Patterns was published, a new topic has become a major consideration for large enterprises: they are under pressure from so-called "digital disruptors" who attack unexpectedly with brand-new business models, operate free of legacy, and release enhanced products on a weekly basis. To compete in the digital age, traditional enterprises must transform not only their business model but also their IT departments.
I collected my experience as chief architect into a book to help IT architects or CTOs combine superb technical, communication, and organizational skill to successfully drive IT transformation in large organizations. The book titled 37 Things One Architect Knows About IT Transformation is available as E-Book on leanpub.com or as print book on lulu.com.
Why Do We Need Integration?
Today's business applications rarely live in isolation. Users expect instant access to all business functions an enterprise can offer, regardless of which system the functionality may reside in. This requires disparate applications to be connected into a larger, integrated solution, which is generally achieved through some form of "middleware". Middleware provides the "plumbing" such as data transport, data transformation, and routing.
What Makes Integration so Hard?
Architecting integration solutions is a complex task. There are many conflicting drivers and even more possible 'right' solutions. Whether the architecture was in fact a good choice usually is not known until many months or even years later, when inevitable changes and additions put the original architecture to test. Unfortunately, there is no "cookbook" for enterprise integration solutions. Most integration vendors provide methodologies and best practices, but these instructions tend to be very much geared towards the vendor-provided tool set and often lack treatment of the bigger picture, including underlying guidelines, principles and best practices.
Asynchronous Messaging Architectures
Asynchronous messaging architectures have proven to be the best strategy for enterprise integration because they allow for a loosely coupled solution that overcomes the limitations of remote communication, such as latency and unreliability. That's why most EAI suites and ESB's are based on asynchronous messaging. Unfortunately, asynchronous messaging is not without pitfalls. Many of the assumptions that hold true when developing single, synchronous applications are no longer valid. Vendor-independent design guidance helps developers avoid these pitfalls so they can build robust integration architectures based on asynchronous messaging.
How can Patterns Help?
Patterns are a proven way to capture experts' knowledge in fields where there are no simple “one size fits all” answers, such as application architecture, object-oriented design, or message-oriented integration . Each pattern tackles a specific problem by discussing design considerations and presenting an elegant solution that balances the forces. Often the solution is not the first approach that comes to mind, but one that has evolved through actual use over time. As a result, each pattern incorporates the experience that senior developers and architects have gained by repeatedly building solutions and learning from their mistakes. Thus, patterns are not “invented” but discovered and observed from actual practice.
What am I Reading Right Now?
|© 2016 • All rights reserved.|