Hybrid integration reference architecture
- 2. Digital Applications
Common use cases for hybrid integration within digital transformation
APIs
1
A. Join the API Economy B. Productivity C. Refactor for innovation
Automa,on
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.
- 3. Business
projects are
driving the
“hybrid”
agenda
Hybrid Integration Styles
Combining app integration,
api integration and data integration
Hybrid Deployment
Software can be flexibly deployed on cloud
and on-premises to optimize solution
architecture
Hybrid Connectivity
Reach across secure connections to get to
data where it is from wherever you need
2
Hybrid User Communities
Used by both IT as well as LOB who are
adopting integration tooling to automate
application interactions.
- 4. 3Page© 2015 IBM Corporation
Overall integration “surface area”
Enterprise Ownership Boundary
Applications on
dedicated Cloud
Applications on
public cloud
SaaS
applications
Customers Business Partners
Applications on-Premise
Applications on
local Cloud
Customers
Customers
Business Partners
Business Partners
- 5. Hybrid Integration Reference Architecture – Basic single gateway
4
{ }
{ }
NoSQL
{ }
{ }
NoSQL
API
Composition
SoR
Core
Business
Operations
Empowering
Digital teams
Systems of
Engagement
Business logic
XaaS
On-Premise
Cloudaffinity
SoR
Low level connectivity
Events
Data
Synchronisation
API & Event Gateway
SoR
- 7. Hybrid Integration Reference Architecture – Basic two gateways
6
{ }
{ }
NoSQL
{ }
{ }
NoSQL
API
Composition
SoR
Core
Business
Operations
Empowering
Digital teams
Systems of
Engagement
Business logic
Mobile Partners
SaaS
Offerings
API
Economy IoT XaaS
On-Premise
Cloudaffinity
SoR
Low level connectivity
Events
Data
Synchronisation
API & Event Gateway
API & Event Gateway
HybridIntegration
SoR
- 8. Simple integration
capability for the
citizen integrator
Full featured
Integration
Middleware
Sophisticated
integration for the
technical user
Richness of Integration Function
IBM is
investing to
enhance and
extend it’s
offerings
for the full
continuum of
users
7
SaaS App
Power
User
DBA /
System
Admin
Application
Integration
Specialist
DeveloperSaaS
Application
Users
Data
Scientist
IT
LOB
- 9. The long tail of integrations
8
Cost/complexity
Candidates for traditional deep
enterprise integration
High
Business benefit
Low
Candidates for
business user integration
(iSaaS)
Candidates for
shadow IT integration
(iPaaS)
- 10. Hybrid Integration Reference Architecture – Bi-modal Integration
9
{ }
{ }
NoSQL
{ }
{ }
NoSQL
API Composition
SoR
Core
Business
Operations
Empowering
Digital teams
Systems of
Engagement
Business logic
Mobile Partners
SaaS
Offerings
API
Economy IoT XaaS
On-Premise
Cloudaffinity
SoR
“Low level” connectivity
Events Data Synchronisation
HybridIntegration
SoR
API & Event Gateway
API & Event Gateway
SoR SoR
API
Composition
Events
Data
Sync.
“Digital” connectivity
- 11. A glimpse into the complexities of a real integration architecture
10
Systems
ofRecord
Integration Hub
Integration Hub
Adapter Adapter
Traditional
Engagement
Applications
Microservice
applications
SaaSApplications
(external)
Adapter
Externally Exposed Services/APIs
Exposure Gateway (internal)
Exposure Gateway (external)
Business
Partners
- 12. Hybrid Integration Reference Architecture – Decentralised
11
{ }
{ }
NoSQL
{ }
{ }
NoSQL
Mobile Partners
SaaS
Offerings
API
Economy IoT
SoR SoR
SaaS
SoR
SoR
SaaS
SoR
SaaS
SoR
SaaS
SoR
SaaS
SoR
SaaS
SoR
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
- 13. 12
IBM – Hybrid integration vision
Connect Seamlessly!
Hundreds of end points to apps and data
in the cloud and on premise
Develop Rapidly!
Intuitive 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
PaaS
On-Premise
CONNECT
XFORM
DELIVER
COMPOSE
EXPOSE
API
MANAGEMENT
SECURE GATEWAY
INTEGRATION
ENGINE
DESIGN - OPERATE - MANAGE - MONITOR - GOVERN
Data
APIs
Apps
TH
GS
IN
MESSAGE &
EVENT HUB
One cohesive offering
serving all integration needs
- 15. Hybrid Integration Styles
Combining app integration,
api integration and data integration
Hybrid Deployment
Software can be flexibly deployed
on cloud and on-premises to
optimize solution architecture
Hybrid Connectivity
Reach across secure connections
to get to data where it is from
wherever you need
Hybrid User Communities
Used by both IT as well as LOB who
are adopting integration tooling to
automate application interactions.
- 16. 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 products
http://www.ibm.com/middleware/us-en/solutions/hybrid-integration
“Microservices, SOA, and APIs: Friends or enemies?”
https://ibm.biz/MicroservicesVsSoa