Enterprise Integration Design Patterns

Editing Enterprise Integration Design Pattern(EIP) focuses on messaging patterns for enterprise application integration (EAI). Messaging makes it easier for programs to communicate across different programming environments (languages, compilers, and operating systems) because the only thing that each environment needs to understand is the common messaging format and protocol.

Messaging patterns define the means by which different elements in a message-passing system connect and communicate to enable interaction among objects within programs and among various types of software -- which may be written in different languages and exist on different platforms in multiple locations.[1]

First of all we should define EIPs and why we should use them. As the name implies, these are tested solutions for specific design problems encountered during many years in the development of IT systems. And what is all the more important is that they are technology-agnostic which means it does not matter what programming language or operating system you use. Patterns are divided into seven sections:

  • Messaging Systems,
  • Messaging Channels,
  • Message Constructions,
  • Message Routing,
  • Message Transformation,
  • Messaging endpoints,
  • System management.

ESB

Mule ESB

WSO2 ESB

Apache Camel

source: https://dzone.com/articles/enterprise-integration

       https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns