apidays Paris 2022 - APIs the next 10 years: Software, Society, Sovereignty, Sustainability December 14, 15 & 16, 2022 Trends, patterns and use cases in hybrid cloud API Management Matt Roberts, Distinguished Engineer and CTO at IBM Integration ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/ Deep dive into the API industry with our reports: https://www.apidays.global/industry-reports/ Subscribe to our global newsletter: https://apidays.typeform.com/to/i1MPEW

1. Trends, patterns and use cases
in hybrid cloud API Management
Matt Roberts
Distinguished Engineer and CTO, IBM Integration

2. 2023 SERIES OF EVENT
New York
May 16&17
Australia
October 11&12
Singapore
April 12&13
Helsinki & North
June 5&6
Paris
SEPTEMBER
London
November
15&16
June 28-30
SILICON VALLEY
March 14&15
Dubai & Middle East
February 22&23

3. Goals for this session
Why are hybrid-cloud API scenarios permeating the industry?
What are the different hybrid-cloud API management patterns?
Why is API portability a critical factor in delivering successful hybrid-cloud
projects?
2

4. 16%
% of business
channels replaced
by digital
34% 2020
2019
Over 50%
of organizations estimate
they have more than
100 applications in their
portfolio today
The great
digital shift
Growing
complexity
- McKinsey
10 years
of digitization
in under 1 year
- IDC
Why are hybrid-cloud API
scenarios permeating the
industry today?
3

5. Patterns of hybrid-cloud API management
4
D
Hybrid runtimes
Synchronized or replicated
instances in multiple locations
to provide extra capacity,
“burst” style scenarios, or
HA/DR capability.
C
Hybrid deployment
Separating the components of
your API management
provider, often a centrally
managed control plane with
runtime gateway close to your
application endpoints.
E
Hybrid management
With the increasing number of
instances in different locations
and providers it becomes
important to manage those
efficiently across your estate.
A
Single deployment
Typical starting point, often on-
premises. Easy to manage and
maintain given the limited
scope.
B
Multiple deployments
Different (unrelated) APIs
running elsewhere, often in a
public cloud provider as part of a
digital transformation project or
similar.

6. Technical considerations for
hybrid-cloud API management
5
API
portability
Flexibility of
deployment
topologies
Automation
Operational
simplicity
Runtime state
replication
Security

7. Runtime state replication
for high availability or bursting

8. High availability use cases – active / passive
7
API-1
On-premises data
centre
API-1
Public cloud
provider
Applications
(separate API
platform instance,
for resilience)

9. High availability use cases – active / passive
8
API-1
On-premises data
centre
API-1
Public cloud
provider
Applications
(failover)

10. High availability use cases – active / passive
9
API-1
On-premises data
centre
API-1
Public cloud
provider
Applications
(failover)
• But what kind of data replication did
we have to put in place to enable this
scenario?
• API definitions
• Relatively static
• Deploy to both instances using same
CI/CD pipeline
• Application subscriptions
• Static scenarios
• Dynamic scenarios (easy for active/passive)

11. Burst traffic use cases
10
API-1
On-premises data
centre
API-1
Public cloud
provider
Applications
(handling excess
traffic workload)
• Second location handles the excess traffic
• Either by redirect (pictured)
• or GLB workload distribution
• Again, API definition and subscription data
can be replicated lazily as burst traffic is an
exceptional occurrence

12. High availability use cases – active / active
11
API-1
API-1
On-premises data
centre
Public cloud
provider
Applications
• Active distribution of traffic to both
deployments
• API definition still replicated via CI/CD
• What about Subscriptions?
• How quickly does a new subscription
need to take effect in both
deployments?

13. API portability
for hybrid cloud deployments

14. Achieving portability of APIs (a UK banking case study)
13
• Multiple hosting providers for on-premises and cloud built up over time
• Regulatory requirements to avoid lock-in to any individual hosting provider
• Exposing the same logical API from each location for resilience
Data centre provider
1
Data centre
provider 2
Public cloud
provider 1
Public cloud
provider 2
API provider A API provider B API provider C API provider D
API implementation converter (custom written code)
Abstract API definition
Built, owned
and
maintained
by the bank
Forces lowest common
denominator functionality
across all providers

15. Achieving portability of APIs (a UK banking case study)
14
Data centre provider
1
Data centre
provider 2
Public cloud
provider 1
Public cloud
provider 2
API provider A API provider A API provider A API provider A
Built, owned
and
maintained
by the bank
Use the same powerful
features in all locations
Concrete API definition

16. The hybrid cloud API Management platform, from
IBM
© 2022 IBM Corporation 15
IBM API Connect
SaaS
Consume as a service
with multiple options for
isolation and availability
IBM API Connect
Software
Deploy on-prem or any cloud,
bring your own OpenShift,
other K8s platforms or VMware
IBM Cloud Pak
for Integration
Consume API Management
integration capabilities in a
unified integration platform,
on OpenShift anywhere

17. Summary
16
• Hybrid-cloud API Management is increasingly common due to the
breadth and depth of API use cases
• There are a range of patterns and use cases that can be adopted by
different organizations to meet their requirements
• API portability is a critical factor for hybrid success when selecting your
hybrid cloud API Management platform

18. Thank you
Matt Roberts
Distinguished Engineer and CTO, IBM Integration
https://www.linkedin.com/in/matrober/