apidays LIVE Hong Kong - The Open API Economy: Finance-as-a-Service & API Ecosystems Orchestrating APIs at Scale Hieu Nguyen Nhu , Senior Cloud Native Technical Specialist at Microsoft

2. APIM Overview
Enterprise Landing zone
Self-hosted Gateway
K8s API integration
Q & A

3. APIs

4. Frictionless consumption
Self-service user onboarding
Front door
Single point of ingress
Façade
Hide backends from frontends
Move backends without impacting frontends
Re-architect backends without impact on frontends
Expose a subset of backend capabilities
Aggregate or slice backends into APIs
Modernize legacy backends
Decouple frontend developers with mocks
Route
Authenticate
Authorize
Throttle
Transform
Trace
Meter
Discover APIs
Learn how to use APIs
Try APIs without writing any code
Request and receive access to APIs
Download API specs, samples, and SDKs
Interact with the API provider
Get usage reports

5. Developer portal
Gateway
Management
plane
API
Abstract
Secure and protect
Revise and version
Monitor and measure
Publish and monetizeAPI providersApp developers
Discover
Learn
Try
Onboard
Get help
Apps on devices Services

6. http://www.lifedaily.com

10. production environment
Landing
zones logic
Inner loop
Test
Debug
VSCode
Dev
subscription
rover
Azure Pipelines
Business tier
Web tier
Azure
Monitor
CI/CD
Landing
zones
configuration
dev, qa, etc. environment
Business tier
Web tier
rover

11. Multi Tenant - Multi Subscription
Subsidiary2 Subsidiary3
APIM Service
Subsidiary1
APIM Service
SEA
A1 A2
EA
A1 A2
Subsidiary1
APIM Service
L2 Layer
Application
L3 Layer API Config
Pipeline
APIM Service
SEA
A3 A4
EA
A3 A4
SEA
A5 A5
EA
A6 A6

13. General facts:
• Interface – parametrized DevOps pipeline;
• Can be triggered by operator or robot (webhook) as part of CD;
• Integrated with CMDB and uses external URL for API schema and policy;
• “sync-process” interacts with particular Subsidiary APIM service;
• Always generates a new API resource revision, activate it, and update API policy.
DevOps pipeline
sync-process
Operators
(DevOps pipeline)
API Resource Schema/
API Policy
Run “apim-api-sync”
Subsidiary Tenant
CMDB
APIM service
validate appRef
fetch info
create API resource

14. app_ref | your uniq application id | aksale
api_source_url | link to file with API definitions (JSON) | https://bar/foo.json
policy_source_url | lint to file with API policies (XML) | https://bar/baz.xml
products | APIM service products value (list) | []
tags | Arbitrary API tags (list) | []
APIM
Service
(Subsidiary Tenant)
API Resource
appRef 1
• Resources (res1, res2, res3);
• Policy (Inbound/Outbound);
• Backend(s) URL;
API Resource
appRef 2
• Resources (res1, res2, res3);
• Policy (Inbound/Outbound);
• Backend(s) URL;
API Resource
appRef 3
• Resources (res1, res2, res3);
• Policy (Inbound/Outbound);
• Backend(s) URL;

15. Microsoft proprietary and confidential
https://aka.ms/apimupdates
4-6 weeks release cycle. Azure and Developer portal updates are released more frequently.

18. Management
plane
Gateway Dev portal

19. Management
plane
Gateway Dev portal

20. Service
invocation
State
management
Publish
Subscribe
Resource
bindings
Virtual
Actors
Observability Secrets Extensible
Any Cloud or Edge infrastructure
HTTP API gRPC API
Application code
Any code or
framework…
Microservices written in
Dapr: Distributed Application Runtime
Build apps using any language with any framework

21. Gateway pod Gateway pod
API Managers
Kubernetes cluster 1
App 1 pod
Sidecar
User App
App 2 pod
Sidecar
User App
Legend:
Control Plane
Data Plane
Dapr integration policies PREVIEW
Diagram by Mark Chmarny @mchmarny
Self-hosted gateway 1
Sidecar
API Management
Kubernetes cluster 2
App 1 pod
Sidecar
User App
App 3 pod
Sidecar
User App
Self-hosted gateway 2
Sidecar
API Consumers

22. Microsoft proprietary and confidential
https://aka.ms/apimlove
https://azure.microsoft.com/en-
us/resources/apis-and-microservices/

23. Microsoft proprietary and confidential
Appendix

24. Microsoft proprietary and confidential
overview
API-driven development with Kubernetes:
Putting API at the center of the development process to clearly separate app accessibility and app logic
API defines how internal world
communicates with outside world
• External interface to the world
• Formalizes parameters for internal and external
user access
• Allows definition and enforcement of policies,
like security and usage
• Provides abstraction of the underlying details
• Enables decoupling of interface development
from logic development
• Acts as proxy for app logic
Kubernetes provides app orchestration
environment and scalability needs
• Simplifies migration and modernization
• Enables developers to focus on app logic
• Provides orchestration and scalability across
apps and services
Kubernetes platform
Kubernetes
Security, governance, identity
Infrastructure automation
Infrastructure
Accessibility Logic
Cloud app Website
Mobile app B2B partner
API

25. Microsoft proprietary and confidential
API-driven development with Kubernetes:
1. API is defined by API developers and
published via the API Management portal
Kubernetes platform
Kubernetes
Security, governance, identity
Infrastructure automation
Infrastructure
Accessibility Logic
2. Application developers define the
microservices and associated logic
and deploy to Kubernetes
3. API users (internal and/or external) use
the API developer portal to learn about
the API and use them in their applications
4. Applications access APIs via the API
Gateway
5. API Gateway, after ensuring the API
request meets security and other policies
e.g. throttling, forwards the request to
service running in Kubernetes
API
API
developers
API
users
App
developers
Management
Portal
Developer
Portal
Gateway
architecture
Putting API at the center of the development process to clearly separate app accessibility and app logic

26. Questions
Photo by Ilkka Kärkkäinen on Unsplash