mule esb integration patterns

Emerging Tech Series E: Knowledge Management automation of impacts

MULE ESB: Integration Patterns

Name: Rajesh

Architectural styles

Service oriented architecture (SOA)

An architectural style that supports service-orientation. Service-orientation is a

way of thinking in terms of services and service-based development and the

outcomes of services.

Integration Patterns

Existing integration solutions are often modeled after either business processes/functionalities or data flows

A combination of both is not common and could be difficult to design and implement

Most integration solutions architecture can be deducted into just a few common patterns

Migration

Broadcast

Aggregation

Bi-directional synchronization

Correlation

Migration pattern

Most common pattern

Data migration is moving a specific set of data at a particular point in time from one system to another

Migration pattern allows developers to build automated migration services that create functionality to be shared across numerous teams in an organization

Implementation can be record-by-record or in batch

System ASystem B

Broadcast pattern

Data moved/sent from a single source to multiple destination systems

Most common use case is keeping data up-to-date between multiple systems

Usually implemented as one-way synchronization from one to many

System ASystem C

System DSystem B

Aggregation pattern

Takes or receives data from multiple systems and copies or moves it into just one system

Enables the extraction and processing of data from multiple systems and merging them into one application

System DSystem B

System CSystem A

Bi-directional synchronization pattern

Unites multiple datasets in multiple different systems, causing them to behave as one system while allowing them to recognize the existence of different datasets

Enables both systems to be used and maintains a consistent realtime view of the data across systems

This integration patterns is advantageous when object representations of reality must be comprehensive and consistent

System B

System A

End

2013 Infosys Limited, Bangalore, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice. Infosys acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted, neither this documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.

Click to edit Master title style

Click to edit Master text styles

Second level

Third level

Fourth level

Fifth level

12/28/2016


Click to edit Master subtitle style



Second level

Third level

Fourth level

Fifth level





Second level

Third level

Fourth level

Fifth level


Second level

Third level

Fourth level

Fifth level




Second level

Third level

Fourth level

Fifth level



Second level

Third level

Fourth level

Fifth level




Second level

Third level

Fourth level

Fifth level



Click icon to add picture





12/28/2016



12/28/2016




12/28/2016



12/28/2016








12/28/2016











12/28/2016



Second level

Third level

Fourth level

Fifth level



Second level

Third level

Fourth level

Fifth level

mule esb integration patterns

Technology