The document discusses evolution of integration patterns during cloud transformations. It describes how traditional on-premise integration patterns need to adapt when applications and data are deployed in public, private or hybrid cloud environments. Some key challenges addressed include dealing with decentralized cloud services, security issues with exposing systems to the internet, and transforming messaging patterns to use cloud-native services. The document advocates an approach of first re-hosting existing integrations in a cloud-native way to decouple dependencies before further refactoring patterns based on a multi-cloud strategy and API-led architecture principles.

1. Evolution of Integration Patterns

2. I bring around 12 years of general IT experience and expertise in delivering
the solutions on Integration & API Management (on-prem, Hybrid, Multi
Cloud Integration), IoT & Analytics and Microservices & DevOps portfolios. I
have proven experience in a variety of engagements that include Technical
Consulting, Project Delivery and Solution Architecture.
In My Current Role as an Architect – I support customers for Hybrid Multi-
Cloud Initiatives.

3. I N T R O D U C T I O N
H Y B R I D
D E P L O Y M E N T S
M U L T I - F A C E D
C H A L L E N G E S
Quick Recap of Cloud
Computing
Deployments to Public
Cloud – iPaaS/Cloud
Native, Private Cloud
Challenges & Mitigations
during Cloud
Transformations
C L O U D
T R A N S F O R M A T I O N
I N T E G R A T I O N
P A T T E R N S
6R’s for Transformation Evolution of Integration
patterns during Cloud
Transformation

4. PUBLIC CLOUD PRIVATE CLOUD
MULTI CLOUD HYBIRD MULTI-CLOUD
SaaS
App
PaaS
PaaS
Things
VPC
VPC
Custom
Things
PaaS
SaaS
App
PaaS
PaaS
Thi
ngs
VPC
VPC
Custom
Things
PaaS
High Scalability, no upfront costs More Control, Better Security
Flexibility to choose right Services,
Avoid Vendor Lock-in, High
Availability
SaaS
App
PaaS
PaaS
Things
VPC
VPC
Custom
Things
PaaS
SaaS
App
PaaS
PaaS
Things
VPC
VPC
Custom
Things
PaaS
Multi-Cloud Integrated to and from
with Traditional In-house Data
Centers, Legacy Apps

5. What should be the right deployment model?
How does the Integration patterns transform?
Is it only about Integrating Applications, Partner,
Data, API Integration?

6. DE-CENTRALIZED SAAS, PAAS OFFERINGS
SERVICES - TIGHTLY COUPLED INTERACTION STYLES,
TECHNOLOGIES, INCONSISTENT DATA FORMATS
INFINITE ENDPOINTS
HYBRID USER COMMUNITIES DISTINCT INTEGRATION PATTERNS
DISCONNECTED NETWORKS SECURITY

7. Retain
(Encapsulate)
Rehost
(lift and Shift)
Rebuild / Replace
(drop & shop)
Re-platform
(lift-think-shift)
Refactor / Re-architect
(lift & re-shape)
Effort
(Time & Cost)
Opportunity to
Optimize, Business
Benefits
Increased
complexity
6 R’S STRATEGY
Consolidation
Assess the needs
of Integration &
Deployments
Transformation
Focused on
chosen
Deployment
Model
Re-define the
Patterns,
Governance
Optimization
Optimize - Cost,
Integration
Patterns,
Security
Onboard
Governance –
DevOps,
Monitoring,
Analytics
Layout Roadmap
for future

8. On-Premise
Files
Data Sources
APIs
Events

9. Public Cloud iPaaS
Hybrid Network Link
On-Premise
Internet

10. WEBMETHODS.IO IPAAS
Integration Platform as a Service
SELF MANAGED INTEGRATION PLATFORM
Deployed as Cloud Native Deployment either on
Public/Private Cloud

11. webMethods Integration Server Bus
Native Low level Connectivity
Hybrid Connectivity
ERP LEGACY CUSTOM SCM
Microservices
webMethods EDGE API Gateway
Traditional Deployments
Enterprise Network
(Legacy)
Custom
Application
PUBLIC CLOUD
PRIVATE CLOUD
SaaS App
Social App PaaS
PaaS
Things Custom
Things
Rehosted, Re-platformed, Refactored (CaaS, Custom)
Public endpoints
wM Micro Gateway
Providers Network / Hybrid Deployment
webMethods.io
Integration
AD-HOC
DEVELOPER
CITIZEN
DEVELOPER
PROFESSIONAL
DEVELOPER
API MANAGEMENT & GOVERNANCE
Cloud Container webMethods.io B2B webMethods.io API
DEVOPS
MONITORING

12. Common Services
Analytics Tier
Monitoring
DevOps
Security &
Identity
Management
Experience
APIs
Integration Platform
on Cloud
webMethods API Portal
(Design-time)
webMethods API Gateway
(Run-time)
Process
APIs
System
APIs Native Low level Connectivity
Visual
Analytics
On-
premise
webMethods IS, UM,
Adapters
B2B, BPMS, BRE, MFT
webMethods Sync &
Async APIs
Syst
em1
webMethods Edge API Gateway
(Run-time)
webMethods Integration Server Bus
Native Low level Connectivity
Syst
em1
wM Micro
Gateway
Custom
Application
Data lake
Hybrid Network Connectivity
Sa
aS
Ap
p P
aa
S
P
aa
S
Thi
ng
s
V
P
C
V
P
C
Cus
tom
Thi
ngs
Pa
aS

13. IPAAS
• Hybrid User Communities developing Integrations – Integration
Specialists, Ad-hoc Integrators, Citizen Integrators, Digital
Integrators
• Green field implementations has an added advantage of
considering full iPaaS
• Operational Overhead needs to be reduced
SELF MANAGED
• Traditional landscape already have tons of Integrations
running on webMethods
• SLAs, Data regularities are strict
• Want to have full control of entire infrastructure, version of
webMethods, runtime, licensing
• Integration Patterns, workload has strong influence

14. App A App B
E
x
p
o
r
t
I
m
p
o
r
t
Data
App A App B App C
DB
App A App B App C
Event Event Event
Event Bus
App A App B
S
t
u
b
S
k
e
l
e
t
o
n
File Transfer Pattern Shared Database Pattern
Messaging Pattern API Pattern

15. App A App B
E
x
p
o
r
t
I
m
p
o
r
t
Data
• Traditionally file transfers are done using – File Pooling, SFTP, FTP, Email Ports, local files, etc.
• This pattern has impact during the cloud transformation, these needs to be refactored with Cloud Storage
providers. Ex – S3, Azure Blob Storage, etc.
• Cloud storage comes with a cost, don’t save the files in the native format. Use compression techniques. Ex –
Apache Parquet, archives, etc.
Dataset Size on Amazon S3 Query Run Time Data Scanned Cost
Data stored as CSV
files
1 TB 236 seconds 1.15 TB $5.75
Data stored in Apache
Parquet Format
130 GB 6.78 seconds 2.51 GB $0.01
Savings 87% less when using
Parquet
34x faster 99% less data
scanned
99.7% savings

16. • Exposing System of Record over internet?, strict security measures required – e.g., SSL Authentication.
• APIfy the DB access (possible with a microservice ☺)
App A App B App C
SSL
DB
SSL SSL
App A App B App C
DB
APIs

17. App A App B App C
Event Event Event
SQS, Pub-nub, Azure
Service Bus
• Identify the consumers – Internal/External/Hybrid
• External/Hybrid consumers needs to have matured messaging integration. Ex – SQS, pub-nub, etc
• Hosting and exposing messaging endpoint in self managed deployments is not seen often. But is still in use
for internal consumers
• Plan to use webhooks/call-backs for the even driven patterns
App A App B
Subscribe/register
webhook

18. App A App B
S
t
u
b
S
k
e
l
e
t
o
n
• Can be used without any changes to this pattern
• Adopt fail-fast, design for failure approaches
• Enforce straight consumer, API runtime Governances
• API-led architecture is key for building re-usable APIs
• Resource Oriented Architecture help to govern
• Cloud Connectors are the true champions

19. On-Premise
Files
Data Sources
APIs
Events

20. Public/Private Cloud with
Integration Runtime
Hybrid Network Link
On-Premise

21. Public/Private Cloud with
Integration Runtime
iPaaS
Hybrid Network Link
On-Premise
Internet

22. • If you already have an existing
implementation, plan for Cloud Native
Hosting as a first step.
• This would help to de-couple the tightly
coupled integrations.
• Cloud Native hosting also helps achieve
Multi Cloud Deployments seamlessly.

23. Watchout for this space Next Session - Cloud Native Transformations - Challenges and
Mitigations in Deploying Integration workloads to AKS