This slide deck explores the benefits of a hybrid deployment model for managing APIs, whether it's the right option for you, how the WSO2 hybrid API management solution works, and more.

1. Software Architect, WSO2
Hybrid API Management:
API Microgateways Everywhere
Sanjeewa Malalgoda

2. ● API Management
● WSO2 API Manager components
● On-premise API Management
● Cloud API Management
● Hybrid Cloud API Management
○ Deployment Scenarios
● Role of Microgateway in Hybrid API Management.
● WSO2 Microgateway
Agenda

3. API Management
.

4. API Management
People Apps
APIs and
Integration
Services
and Data

5. API Management
Gateway
Access Token Signed JWT
Security
Rate Limiting
Integration
Analytics

6. WSO2 API Manager
Components
.

7. API Manager Components

8. API Manager - User Flows

9. On-premise API
Management

10. ● Deploy WSO2 API Manager within the enterprise network
● Usually external parties do not consume APIs and it’s only
used internally when this pattern is followed
● Sometimes on-premise deployments help to address some
security concerns
On-premise Model

11. On-premise Model
<<Enterprise Network>>
<<Backend Services>>
api.internal.com
Delivery channels

12. On-premise Model
<<Enterprise Network>>
<<Backend Services>>
api.internal.com
api.public.com
Delivery channels
Delivery channels

13. ● Complete control over deployment
● Easier integration
● Reduced latency of traffic for close proximity services
● Keeps API traffic within the enterprise-approved boundaries
because of security or compliance purposes
● Continued message processing even if the internet
connection is lost
On-premise Model - Pros

14. ● High total cost of ownership (deployment and management
complexity)
● Difficult to collaborate with external parties
● Difficult to implement disaster recovery and failover
● Difficult to scale when demand goes high
On-premise Model - Cons

15. Cloud API
Management

16. ● All API calls go through the cloud
● Deployment management addressed in the cloud
● There can be multiple cloud options (consumer-oriented
view)
○ API management deployment which is setup on cloud infrastructure
(private)
○ Cloud API management offering publicly
Cloud Model

17. Cloud Model
<<Backend Services>>
api.internal.com
api.public.com
Delivery channels
Cloud
Deployment

18. Cloud Model
<<Backend Services>>
api.internal.com
api.public.com
Delivery channels
Cloud
Deployment
Non Cloud
Data/Services
<<Backend Services>>

19. ● Cost effective (shared resources)
● Easy to manage (infrastructure management)
● Patching, updating, etc. will be taken care of by the solution
owner
● Easy to scale, disaster recovery
Cloud Model - Pros

20. ● Inefficient if both the backend service and the API consumer
is in same network
● Backend system and data need to be exposed to the internet
if the API management solution resides in the public cloud
● Some internal security measures don’t allow you to deploy
some components in public cloud deployments
● Regional sensitive data and regulations
Cloud Model - Cons

21. Hybrid API
Management

22. ● Get advantages of both on-premise and cloud deployment
models
● Deploy selected components in a regional or on-premise
data center
● Most of the time these regional, on-premise deployment will
have only the gateway runtime
Hybrid API Management

23. Hybrid API Management
<<Enterprise Network>>
<<Backend Services>>
<<Pull API & Throttling Metadata>>
<<Upload Usage>>
api.internal.com
<<Key Validation>>
api.public.com
Cloud
DeploymentDelivery channels
Delivery channels

24. Hybrid API Management
<<Enterprise Network>>
<<Pull API & throttling metadata>>
<<Upload Usage>>
api.internal.com
<<Key Validation>>
api.public.com
Health API
<<Health
Service>>
Private Jet Mode
Cloud
Deployment
Delivery channels

25. Hybrid API Management
<<Enterprise Network>>
<<Pull API & Throttling Metadata>>
<<Upload Usage>>
api.internal.com
<<Key Validation>>
Health API
<<Health
Service>>
Sidecar Mode
api.public.com
Cloud
Deployment
Delivery channels

26. Hybrid API Management
<<Enterprise Network>>
<<Pull API & Throttling Metadata>>
<<Upload Usage>>
api.internal.com
<<Key Validation>>
Health API
<<Health Service>>
Centralized Gateway
<<Weather Service>>
api.public.com
Cloud
DeploymentDelivery channels
Weather API

27. Multi Cloud Integration

28. Role of
Microgateway in
Hybrid API
Management

29. ● Microgateway is a secure, HTTP-based lightweight message
processor for APIs. It is mainly responsible for applying
quality of services to service calls
● It may have the same feature set or subset of features
available in an API gateway
● Natively supports microservice architecture
What is Microgateway

30. ● Regional, on-premise deployment contains just a gateway
runtime
● To deploy gateways in regional or on-prem deployments
○ Small startup time
○ Less resource consumption
○ Easy to configure and manage
○ DevOps friendly
○ Ability to run in a lockdown environment
● Microgateway addresses most of these requirements
Role of Microgateway in Hybrid API
Management

31. ● Scale API gateway runtime within highly decentralized
environments, including microservices architectures
● Easily deployable and configurable by developers at design
time and integrates with DevOps toolchains for scripted
production deployments
● Locked down environments need to have microservice as it
cannot communicate with API Manager
Role of Microgateway in Hybrid API
Management

32. Microgateways Everywhere
IoT device
Workstation

33. WSO2 API Manager
Microgateway

34. ● Fits microservice architecture and is developer centric
● Low resource consumption and efficient
● Small startup delays
● Dev-Ops friendly (scriptable, container ready)
● Horizontal and elastic scaling
● Immutable, ephemeral
● In-memory metadata and no database access required
● Configurable at deployment time (minimum configurations)
Characteristics of an API Microgateway

35. API Microgateway
API Gateway
API Manager
Microgateway
Toolkit
Microgateway
Artifacts

36. API Microgateway
API Gateway
API Manager
Microgateway
Toolkit
Context
Microgateway
Engineering API
Microgateway
IT API
Microgateway
HR API
Microgateway
Artifacts

37. API Microgateway
API Gateway
API Manager
Microgateway
Toolkit
Context
Microgateway
Engineering API
Microgateway
IT API
Microgateway
HR API
Microgateway
Artifacts
Microgateway
HR API

38. THANK YOU
wso2.com