| EIP Name | EIP Description | Use Case | 
  | Pipes and Filter | Use
  the Pipes and Filters architectural style to divide a larger processing task
  into a sequence of smaller, independent processing steps (Filters) that are
  connected by channels (Pipes). | Pipes and Filter | 
  | Router | Consume
  the message from one channel and forward to another message channel based on
  the condition |  | 
  | Content Based
  Router | Consume
  the message from one channel and examine the message content , based on the
  data/type  need to route to different
  channel .Basically routing based on the content | We
  received the Customer data which inclues the Post Paid /PrePaid based on the
  data it will redirect to either Postpaid channel or Prepaid Channel | 
  | Message
  Filter | Its
  specical kind of router to eliminate the undesired messages based on the
  certain creteria | We
  need to publish the Promotion for certain customer like we have two kind of
  customer Public customer and Enterpriase Customer , We need to send the
  Promotion notification to Enterprise level customer with some promotion code
  .Here we are using Message Filter | 
  | Receiptent
  List | Consume
  the message and forward the message to channel based on the receipents list |  | 
  | Spilitter | Consume
  the composite message and spilit into series of separate message and pass to
  the channel | We
  consume the purchase order from customer which contains the data for several
  system like VAS/Mobile/Date and etc , splitter will split the message into
  indidual message and send to respective channel or system | 
  | Aggregator | Consume
  the complete set of related message and collect /aggregate and send to the
  channel | We
  received the different induval mobile purchase order and combine /collect
  then send to respective channel for further processing | 
  | Message
  Broker | Receive
  the message from multiple channel and route to correct designation
  channel | Customer
  life cycle notification | 
  | Message
  Translator | Translate
  the message from one format to another formate |  | 
  | Content
  Enricher | Special
  kind of translator , we need enhance the missing data before route to the
  final channel | We
  have legacy System as front chnnel and trying to get the data from new BCC
  application. But data format between two systems are different . We have the
  data transformation enhanced the missing data in the request before route to
  designation channel | 
  | Content Filter | Remove
  the unused data from message and route to the respective channel |  | 
  | Cannonical
  Data Model | Its
  data model independent to any application , each application to
  produce/consume in this format | PIM/CDM | 
  | Event Driven
  Consumere |  | Publish
  the customer notification | 
  | P2P Channel | Send
  the message to P2P to ensure that only one receiver successfully received the
  message | Order
  to payment | 
  | Publish and
  Subscribe | One
  input send to multiple output channel , each out put received only one
  time |  | 
  | Dead Letter
  Channel | Failed
  message route to dead letter channel | Message
  route to dead letter queue due to time out /failure/expire and etc ie not
  successfully process the data then it will redirect to dead letter channel .
  Another queue will pick the message then process it | 
  | WireTap | Consume
  and receive message route through this channel , mainly used to
  testing/trouble shooting | Message
  from all core service will be tracked | 
  | Message Bus | Acting
  as middleware between the two system |  | 
  | Message
  Gateway | Encapulate
  the message specific code ie client not able to access the message instead it
  can access through Gateway |  | 
  | Detour | Perform
  the additional steps for incoming message and controlled by the control Bus | Verify
  abd validation | 
  |  |  |  | 
 
Comments
Post a Comment