Enterprise Integration Patterns
Implementing Enterprise Integration Patterns
While integration is inherently complex, one of the major stumbling blocks is the lack of a common vocabulary and body of knowledge around asynchronous messaging architectures used to build integration solutions. Enterprise integration patterns provide a standard notation for describing how to integrate services. They include several design patterns and are fully described in Gregor Hohpe’s book Enterprise Integration Patterns.
Enterprise integration patterns can be implemented with FUSE Mediation Router by employing a consistent vocabulary and visual notation framework to describe large-scale integration solutions across many technologies. FUSE Mediation Router allows you to go from diagram built from predefined enterprise integration patterns to implementation without coding.
With the FUSE Mediation Router, a Java developer can quickly develop enterprise integration patterns by using a simple API directly within a Java program, or in FUSE Integration Designer. These enterprise integration patterns, or integration components, can also be deployed in a number of deployment platforms including the FUSE ESB, providing a seamless migration path to a more formal SOA infrastructure.
Watch a 5 minute video to see architect James Strachan provides a simple demonstration of how to apply standard Enterprise Integration Patterns for content-based routing, message splitting and other patterns, configured in either Java or XML.
The FuseSource team also offers an OSGi, ActiveMQ performance guide, BPEL technology, application integration technology, distributed architecture information and enterprise integration solutions.