Enterprise Integration Design Patterns

From OasisSoftTech.com - Knowledge Base/Java/Springframework/Microservices/Cloud-AWS/AI
Revision as of 04:31, 7 June 2018 by Rasimsen (talk | contribs) (Created page with " 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 t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

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

       https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns
Retrieved from ‘https://knowledgebase.oasissofttech.com/index.php?title=Enterprise_Integration_Design_Patterns&oldid=255’