It integration strategy : Example - Approach

Sample
Organisation ABC IT Integration Strategy
Alignment with Modernization Programs, M&A & Cloud Migration
<<Exec Pack>>
Akshyadeep Raghav
Copyright © MinMax Solutions 1

Agenda
1 Business Motivations for Integration Strategy
2 Integration Strategy
3 Integration Architecture States (Current- Transition- Target)
4 Current Integration Technologies
5 Consolidated Integration Technologies (Target State)
6 Integration Strategy Roadmap
7 Benefits aligned to IT Strategy
9 Appendix

Business Motivation for Integration Strategy
Consolidation of
Integration Technologies
Prefer Use of Own
Products (XYZ Advance
Secure Gateway)
“Prefer Configuration
Rather Code”- No Custom
Integrations Code.
Simplification of
Application Integration –
Limit P2P Interfaces
Future Growth-
Scalability- Availability
Ease to Integrate with
Engineering Systems,
Partners and new Acquiring
Businesses (e.g. BC Merger)
Design of MicroServices
API for integration.

IT Integration Strategy
Technology Consolidation
•EAI
(Tibco/Talend/Mulesoft/Oracle
Fusion etc.)
•EDI & ETL (IBM Sterling/Golden
Gate/ Informatica ETL/
Mulesoft Anypoint B2B et.)
•API Management (Mulesoft/
Tibco)
•API Gateway (Datapower/
Mulesfot)
Interface Simplifications
•Reduce P2P Interfaces
•COTS Connectors rather
Custom Integration
•Control over Data flow Across
Interfaces (Between any two
system)
Aid in future growth of
application
•MicroService APIs for high
volume real time data
movement
•Fault Tolerant Integration with
Limp Mode Provision
•Independent Integration
Modules for greater agility and
development
Integration Governance Process
•Defining Principles & Policies
for adherence for all teams (IT-
Engineering Partnership
Framework).
•Process for Integration
Engagement, Reuse of
Interfaces & Strategic
directions.

Organisation ABC IT Integrations
Current State – Transition – Target State

On Prem Integration Platform
Tibco (Middleware & MFT) + Oracle Fusion Middleware + Talend +
IBM B2B Sterling Integrator
Cloud Integration Platform
MuleSoft + Informatica Cloud +
Relational Junction
Current Integration Architecture
Copyright © MinMax Solutions
6
On Prem Apps- Organisation ABC IT + XYZ IT (Merger Org).
SaaS Apps – Organisation ABC IT + XYZ IT
Customer &
Partner
Apps
CustomApplicationAccessforCustomer&Partners(e.g.PartnerNetPortaletc).
API Gateway (IBM Data Power)
Public API
Enterprise API
API Gateway Internal
API Gateway External
P2P Interface
Engineering System
APIGateway(IBM
DataPower)
APIGateway(IBM
DataPower)
Custom Web services, Apis & SaaS API Connectors
Custom Web service, APIs + Application Connectors
SFDC Zuora Eloqua
LMS- Saba
Cloud Workday
ServiceNow Concur
IDM
(NSL)
Organisation
ABC.com
My
Organisat
ion ABC
Partner
Portal
Common
Console
Finance Applications
Oracle R12
Finance
SabrixRevProIncentive
Comp
Enterprise Databases
EDW ODS
XYZ SystemBlue Store Oracle R12 Blue Touch OnlineKewill Interactive Intelligence Choice, FlashDrupal

Tibco (Middleware & MFT)
MuleSoft
Transition State 1 - Integration Architecture (delivered via Modernisation
Program)
7
On Prem Apps- Organisation ABC IT + XYZ IT
Customer &
Partner
Apps
PublicAPIsforCustomers&Partners(exposingusageinfo,licenseinfo,account
managementetc.)
Public API
Enterprise API
Engineering System
APIGateway(IBM
DataPower)
APIGateway(IBM
DataPower)
SaaS API Connectors
Micro-Services API, Custom Web service, APIs + Application Connectors
SFDC Zuora Eloqua
LMS- Saba
Cloud Workday
ServiceNow Concur
IDM
(NSL)
Organisation
ABC.com
My
Organisat
ion ABC
Partner
Portal
Common
Console
Oracle R12
Finance
Comp
EDW ODS

MuleSoft
Transition State 2 - Integration Architecture (delivered via XYZ
Integration)
8
On Prem Apps- Organisation ABC IT + XYZ IT
Customer &
Partner
Apps
managementetc.)
Public API
Enterprise API
Engineering System
APIGateway(IBM
DataPower)
APIGateway(IBM
DataPower)
SaaS API Connectors
SFDC Zuora Eloqua
LMS- Saba
Cloud Workday
ServiceNow Concur
IDM
(NSL)
Organisation
ABC.com
My
Organisat
ion ABC
Partner
Portal
Common
Console
Oracle R12
Finance
Comp
EDW ODS
XYZ
Systems
Blue Store Oracle R12 Blue Touch OnlineKewill Interactive Intelligence Choice, FlashDrupal

MuleSoft
Transition State 3 - Integration Architecture
(delivered via Cloud Migration.)
9
On Prem Apps- Organisation ABC IT + Bluecoat IT
Customer &
Partner
Apps
managementetc.)
Public API
Enterprise API
Engineering System
APIGateway(IBM
DataPower)
APIGateway(IBM
DataPower)
SaaS API Connectors
SFDC Zuora Eloqua
LMS- Saba
Cloud Workday
ServiceNow
Concur
IDM
(NSL)
Organisation
ABC.com
My
Organisat
ion ABC
Partner
Portal
Common
Console
Oracle R12
Finance
Comp
EDW ODS

Integration Platform (MuleSoft)
Target Integration Architecture
10
Azure Cloud Platform (PaaS + IaaS)
(On Prem Apps- Organisation ABC IT + XYZ IT)
Partner
Apps
managementetc.)
API Gateway (TBC)
Public API
Enterprise API
Engineering System
API Gateway (TBC)
APIGateway(TBC)
APIGateway(TBC)
SaaS API Connectors
Micro-Service APIs (Custom & COTS) & Application Connectors (COTS)
SFDC Zuora Eloqua
LMS- Saba
Cloud Workday
ServiceNow Concur
IDM
(NSL)
Organisation
ABC.com
My
Organisat
ion ABC
Partner
Portal
Common
Console
Oracle R12
Finance
Comp
EDW ODS
XYZ
System
Blue Store Oracle R12 Blue Touch OnlineKewill Interactive Intelligence Choice, FlashDrupal

Integration technologies
Current Technologies to Consolidated Technologies

Current Integration Technologies
Organisation ABC IT & XYZ IT (Merger Organisation)
ESB
(Middleware)
MuleSoft Cloud
Tibco
Informatica Integration Cloud
Oracle Fusion Middleware
Put-IT-Forward
Relational Juction as Middleware
Talend
Web Methods
API Gateway
IBM Datapower
MuleSoft Gateway
EDI & ETL
MuleSoft Cloud (Anypoint
B2B/ Anypoint Partner
Manager)
IBM Sterling B2B
Oracle Golden Gate
Informatica ETL
Relational Junction (SFDC)
API
Management
Mulesoft API management
Tibco API Management
(Lifecycle Management)
File Transfer
Tibco MFT
ABC System
XYZ System

Consolidated Integration Technologies
Organisation ABC IT + XYZ IT (Merger Organisation)
ESB
(Middleware)
MuleSoft
Integration
Platform
API Gateway
(TBC)
IBM
Datapower
EDI & ETL
IBM Sterling
B2B
Oracle Golden
Gate
Informatica
ETL
API
Management
Mulesoft API
management
File Transfer
Tibco MFT

Integration Strategy - Roadmap
Q2, YYYY Q3, YYYY Q4, YYYY Q2, YYYZQ1, YYYY

Benefits aligned to IT Strategy
Save
•Cloud Integration Platform-ESB (Mulesoft)
• De-duplicates Interfaces
• Abstracts app to app dependencies
• Cloud Adaptor available for most the IT Apps
•Microservices
• Faster to implement changes
• True agility in terms of development, deployment & release (independent component & feature)
•Consolidation of Technologies
Secure
• Control over data flow (ease to employ governance, policies etc.)
•Microservices
• Much higher reliability & availability (operates in LIMP mode)
• Improves fault Isolation
Grow
• Faster Integration via Reuse of Interfaces
• Control over Data flow
•Microservices
• Massively scalable APIS for Future Growth (at each tier of application design)

Approach to Implement Integration Strategy
Classification based on Purpose of Applications
in Architecture Landscape

Classification of Application on the basis of functional purpose
17PS: Ignoring Infra Apps for this integration strategy, such as Infrastructure Monitoring System (Connects with other System for Alerts etc.)
•Batch Operation: Nature of operation- Bulk or large volume of data (Data fetch, Data Profiling, Cleansing,
Archive)
•Asynchronous Data Transfer Mode: Sends data to Transactional System, Customer Facing, Backend System
Data Management Systems
•ESB: Connects directly with Customer facing applications – data transfer modes “near real-time”.
•P2P:Connects directly with Customer facing applications – data transfer modes “real-time”.
Transaction based Systems
[Financial System/Inventory Management/Fulfillment-
Cloud Apps or Subscription etc.]
•ESB Integration- Typical e.g. of system “Partner Portal” – near real time data/message requiredCustomer facing applications
•ESB via near real time transfer mode.
•ESB via Batch operation.
Backend applications
[e.g. Fulfillment System – Blue Cote Hardware Products]
•E.g. On Prem App and Cloud Apps have adaptor so brings data to On Prem Environment and than to ESB.
•Abstracts On Prem System via ESB from External System
Data integration applications (TIBCO + Mulesoft) &
connector
•P2P for SSO
•ESB for IDM Data Access
Security & Access Management Systems
•Batch between Data Management & ESBAnalytics & Reporting Systems

Application Clustering based on Functional Purpose
Data Management
Systems
Transaction based
Systems
Customer facing
applications
Backend
applications
Data integration
applications & adapters
Security & Access
Management Systems
Analytics & Reporting
Systems
SFDC
Yes Yes
Eloqua
Yes
Zoura
Yes Yes
EDW
Yes
Hadoop
Yes
BigData
Yes Yes
Tibco
Yes
Mulesoft
Yes
Saba
Yes Yes
Workday
Yes Yes
XYZ Sys
Yes
Organisation
ABC.com
Yes
Client Portal
Yes

Integration Requirements based on Integration
Parameters

Integration Parameters
20
•Real Time ( e.g. event based system -data flow in few seconds)
•Near Real Time (e.g. inventory/stock management -data flows in few min.)
•Batch Operation (e.g. Data archival, Cleansing/ BI system- data flows in hours)
Latency
•Push (e.g. Message Broker/ ESB) –Typically fire & forget integration pattern.
•Pull (e.g. mostly WS calls to data holding system)
Data Movement
[Identifies type of integration-: Message
Broker/WS/ESB]
•Transactions with Response Required- Synchronous – More reliable
•Alert/Notification Message Transaction –the speed of transaction is important than reliability
Data Transfer Mode
[Synch/Asych]
•External Gateway/ Internal Gateway
•Encryption/Protocols
Security
[identifies type of integration via ESB/ P2P/ Cloud
Platform Adaptor- API Gateways-: External/Internal]
•At least Once
•Always Once (duplications is managed by receiving system- like alter to suspend an account)
•Only Once (e.g. Data appending/ Data Quality transitions)
Reliability (of message processing)
•Uni-directional
•Bi-directional
Data flow direction
•Cloud
•P2P
•ESB
Integration Adaptor availability

Application Integration Requirements (based on Integration
Parameters)
Latency
Data Movement
Data Transfer
Mode Security Reliability Data flow direction
Integration
Adapter
Availability
Realtime Near
Realtime
Batch
Operation
Push Pull Synch Asych Atleast Once Always Once Only Once Uni-
directional
Bi-
directional
SFDC Zoura Eloqua EDW 1. Eloqua
2. Mulesoft
Eloqua Partner
Portal
SFDC
Zoura Mulesoft
EDW
Hadoop
BigData
Saba
Workday EDW 1. Mulesoft
XYZ Sys
Organisati
on
ABC.com
Client
Portal

Reference Architecture–Integration Architecture
22
Transactional System
Data Management System
Customer Facing Apps Backend Applications
Data Integration Apps & Connector
Security & Access Management (SSO)
Analytics & Reporting
Engineering System
Batch Synchronous
Batch Asynchronous
P2P Synchronous
P2P Asynchronous
WS Synchronous
WS Asynchronous
Mule Soft
(Cloud Middleware)TIBCO
Data Mgmt & BI Data
Data Mgmt & BI Data
Transaction Data Fulfillment Data
Local Data
(e.g. Payment Response)
Cleansed Data
Data Mgmt & BI Data
SSO Data
SSO Data
SSO DataSSO Data

Application Architecture
Monolithic Vs Microservices Architecture

Microservices Architecture

Microservices Architecture
Key Principles to follow while designing
•Reduce physical
dependencies
•Improve deployment
flexibility
•Automated Failure
detection & notification
•“Limp Mode” operation
of business features
•Minimize availability
coupling
•Improve scaling options
•Horizontal scaling at
every tier
•Functional
Decomposition
Scale out not
up
Prefer
Asynchronous
Integration
Virtualize
components
Design for
failure

Key Benefits and Challenges of Microservices Architecture
• Inter service communication mechanism
to handle.
• Testing is more difficult.
• Use case that span multiple services
without distributed transitions is difficult.
Needs to manage
additional
complexity of
creating &
managing a
distributed system
• Operational complexity of deployment as
system comprised of different service
types.
Deployment
Complexity
• Require investment initially to re-design
custom applications
Re-design cost for
custom application
• Availability
• Reliability
• Massive scalability
Enable Seamless
Growth
• Each service can deployed
independently of other services
• Improves fault Isolation
Deliver quality
functionality
faster
• Independent Changeable
Components (App/Data/Infra
layers)
Eliminated long
term
commitment to a
technology stack
Benefits Challenges

Integration Designs
P2P- File Transfer- Database- ESB (SOA)

ESB Integration (Middleware)
2828
SFDC
Eloqua
Partner Net Portal
Oracle-ERP
EDW
Workday
Enterprise Service Bus
Monitoring/Event
Mgmt
Process Orchestration
Services
Data Services/
Message Broker
Data AbstractionData & Interface Governance
API Mgmt

Key Advantages and Limitations of ESB
Benefits
• Simplification of Application
dependencies, loosely coupled
system.
• Reuse of Interfaces
• Configuration rather writing
integration code
• Scalable Integration to Enterprise
Scale
• A by product advantage is: ESB can
reduce delivery time of projects.
Limitations
• Slower communication speed
compared to DDS/P2P Services,
though do not impact Organisation
ABC IT Integration Needs. (Our
needs are different than Trading
Platforms).
• ESB systems are costly and requires
niche skills to support.
• ESB requires significant investment
in resiliency otherwise it becomes
single point of failure.

It integration strategy : Example - Approach

Recommended

Recommended

More Related Content

Similar to It integration strategy : Example - Approach

Similar to It integration strategy : Example - Approach (20)

Recently uploaded

Recently uploaded (20)

It integration strategy : Example - Approach

Editor's Notes