A Reference Architecturefor Hybrid Integration

Peter BroadhurstSenior Technical Staff Member for IBM App Connect

Digital Applications

Common use cases for hybrid integration within digital transformation

APIs

1

A. Join the API Economy B. Productivity C. Refactor for innovation

Automation

Enable new channels for revenue by monetizing

existing data via the API economy

Enable line of business to automate their own work across SaaS and existing

systems of record

Make a fundamental shift to a composable application

architecture, and cloud-based partners, to enable innovation.

Business projects are driving the “hybrid” agenda

Hybrid Integration StylesCombining app integration, api integration and data integration

Hybrid DeploymentSoftware can be flexibly deployed on cloud and on-premises to optimize solution architecture

Hybrid ConnectivityReach across secure connections to get to data where it is from wherever you need

2

Hybrid User CommunitiesUsed by both IT as well as LOB who are adopting integration tooling to automate application interactions.

3Page© 2015 IBM Corporation

Overall integration “surface area”

Enterprise Ownership Boundary

Applications on dedicated Cloud

Applications on public cloud

SaaSapplications

Customers Business Partners

Applications on-Premise Applications on local Cloud

CustomersCustomersBusiness PartnersBusiness Partners

Hybrid Integration Reference Architecture – Basic single gateway

4

{ }{ }

NoSQL

{ }{ }

NoSQL

API Composition

SoR

CoreBusinessOperations

EmpoweringDigital teams

Systems ofEngagementBusiness logic

XaaS

On-Premise

Clo

ud a

ffini

ty

SoR

Low level connectivity

Events Data Synchronisation

API & Event Gateway

SoR

Custom Apps

DatabasePackaged Apps

Mainframe

SystemAPIs

API Consumption Landscape

InteractionAPIs

System APIsAPIs that access the core systems and assemble data in a standardized form for general consumption

Services

Interaction APIsInvoke one or more System API’s or data sources, and manipulate the returned data

5

Hybrid Integration Reference Architecture – Basic two gateways

6

{ }{ }

NoSQL

{ }{ }

NoSQL

API Composition

SoR

CoreBusinessOperations

EmpoweringDigital teams

Systems ofEngagementBusiness logic

Mobile Partners SaaSOfferings

APIEconomy IoT XaaS

On-Premise

Clo

ud a

ffini

ty

SoR

Low level connectivity

Events Data Synchronisation

API & Event Gateway

API & Event Gateway

Hyb

rid In

tegr

atio

n

SoR

Simple integration capability for the citizen integrator

Full featured Integration Middleware

Sophisticated integration for the

technical user

Richness of Integration FunctionIBM is investing to enhance and extend it’s offerings for the full continuum of users

7

SaaS App Power User

DBA / System Admin

ApplicationIntegration Specialist

Developer

SaaSApplication

Users

Data Scientist

IT

LOB

The long tail of integrations

8

Cos

t/com

plex

ity

Candidates for traditional deepenterprise integration

HighBusiness benefit

Low

Candidates forbusiness user integration

(iSaaS)

Candidates forshadow IT integration

(iPaaS)

Hybrid Integration Reference Architecture – Bi-modal Integration

9

{ }{ }

NoSQL

{ }{ }

NoSQL

API Composition

SoR

CoreBusinessOperations

EmpoweringDigital teams

Systems ofEngagementBusiness logic

Mobile Partners SaaSOfferings

APIEconomy IoT XaaS

On-Premise

Clo

ud a

ffini

ty

SoR

“Low level” connectivity

Events Data SynchronisationHyb

rid In

tegr

atio

n

SoR

API & Event Gateway

API & Event Gateway

SoR SoR

API Composition Events Data

Sync.

“Digital” connectivity

Hybrid Integration Reference Architecture – Decentralised

10

{ }{ }

NoSQL

{ }{ }

NoSQL

Mobile Partners SaaSOfferings

APIEconomy IoT

SoR SoR

SaaSSoR

SoR

SaaSSoR

SaaSSoR

SaaSSoR

SaaSSoR

SaaSSoR

In a perfect world…

• Application teams self-administer exposure of their own APIs

• Access to external APIs is governed using the same mechanisms used to govern access to internal APIs.

• Application teams handle their own integration needs using a productive subset of the tools available

• Application logic is firmly seated with the application teams

• API monitoring/diagnostics are gathered consistently across the organisation

• Security models are implemented more consistently

11

IBM App Connect

1

SimpleNo-code and

low-code approach to integration,

accessible by users of all skill levels

2 3 4

FastPre-built

connectors and templates

for 100s of SaaS and

legacy applications

FlexibleCloud and

on-premises options

to deploy where most convenient

for you

AffordablePay only for

the integration actions you run, with no

extra costs for application connectors.

12

Simple. No-code and low-code approach to integration, accessible by users of all skill levels

Smart Connectors for Cloud and On-premise apps

• Business-friendly metadata for the business user

• Trigger based on both create and update events

• Capture events based on both webhooksand polling mechanisms

• Addition of retrieve (lookup) and update actions

• Dynamic discovery of custom objects

Connectivity with IBM solutions– IBM Integration Bus– IBM Message Hub MessageHub

Fast. Pre-built connectors and templates for 100s of SaaS and legacy applications

14

Flexible. Cloud and on-premises options to deploy where most convenient for you

Public Cloud / SaaS

§ A fully managed, multitenant iPaaS, which auto scales to handle variable workloads

§ Flexible pricing models and option of a dedicated runtime environment on SaaS

Private Cloud / On-premises

§ Buy your own license and deploy on-premises or in a private cloud environment

§ Available as Docker image which offers complete deployment portability

Hybrid Deployment

§ Combine the efficiencies of public cloud with the control of private deployment

§ Flexibility of choosing between SaaS and on-premises deployments

App Connect core platform capabilities

ConnectPre-built connectors for SaaS & on premise systems and other IBM integration and messaging solutions

TransformGraphical mapper for rapid transformation between source and target data formats

DesignConfiguration-based tooling to implement integration logic without having to code

ManageWeb based management and monitoring of integrations

App Connect Designer (new UI)

App Connect Studio (original UI)

IBM Cloud Integration

16

App Connect

API Connect

Integration Bus

MQ

ApplicationIntegrationSuite

IBM App Connect is part of a portfolio

IBMApplicationIntegrationSuite

acomposablearchitectureforhybridintegration

CloudConnectivityü Broadnativecloudconnectorsü Non-specialistcompositionü Pre-definedtemplates

EnterpriseIntegrationü Deepmatureconnectivityü Richflowlanguagesupportü Advancedmediationcapabilities

APIManagementü Policybasedtrafficmanagementü Integrateddeveloperportalü Lifecyclemanagement

A glimpse into the complexities of a real integration architecture

18

Syst

ems

of R

ecor

d

Integration Hub

Integration HubAdapter Adapter

Trad

ition

alEn

gage

men

tA

pplic

atio

ns

Mic

rose

rvic

eap

plic

atio

ns

SaaS

App

licat

ions

(ext

erna

l)

Adapter

Externally Exposed Services/APIs

Exposure Gateway (internal)

Exposure Gateway (external)

Bus

ines

s Pa

rtne

rs

19

IBM – Hybrid integration vision

Connect SeamlesslyHundreds of end points to apps and data in the cloud and on premise

Develop RapidlyIntuitive and robust tooling to transform data to meet business needs

Scale Efficiently Performance and scalability to meet the SLAs of your business applications

HYBRID INTEGRATION

SaaS PaaSOn-Premise

CONNECT XFORM DELIVER COMPOSE EXPOSE

API MANAGEMENT

SECURE GATEWAY

INTEGRATION ENGINE

DESIGN - OPERATE - MANAGE - MONITOR - GOVERN

Data APIsApps TH GSIN

MESSAGE &EVENT HUB

One cohesive offering serving all integration needs

Hybrid Integration StylesCombining app integration, api integration and data integration

Hybrid DeploymentSoftware can be flexibly deployed on cloud and on-premises to optimize solution architecture

Hybrid ConnectivityReach across secure connections to get to data where it is from wherever you need

Hybrid User CommunitiesUsed by both IT as well as LOB who are adopting integration tooling to automate application interactions.

Looking for more information?

These slides come from the following article:

“The evolving hybrid integration reference architecture”https://ibm.biz/HybridIntRefArch

And are described in this video for Integration Developer News http://ibm.biz/HybridIntRefArchYouTube

More information on IBM’s hybrid integration productshttp://www.ibm.com/middleware/us-en/solutions/hybrid-integration

“Microservices, SOA, and APIs: Friends or enemies?”https://ibm.biz/MicroservicesVsSoa