Building a modern microservices application today often requires data and services from multiple clouds (i.e. IBM, AWS, Azure, GCP, on-prem) along with Serverless and traditional Cloud Foundry-based application components. We’ll show you how to get started exposing APIs from Serverless and Cloud Foundry-based applications faster than any other cloud provider. Next, we’ll discuss how to co-locate API Gateways with backends running on any cloud to improve performance and reduce latency.

1. © 2017 IBM Corporation
Deploying Multi-cloud,
Serverless & Cloud Foundry
APIs at Scale
—
Ken Parmelee
Driver of the API Future
Twitter @kparmeleetx

2. Your competition, your opportunity
2© 2017 IBM Corporation
274,000

3. Microservices and APIs are
Products
32017 IBM Corporation
Your APIs must
• Scale to peak consumption
• Be Reliable- Stability and uptime
• Be Secure
• Be Performant
• No weak dependent services
• Throttling
• Drive interest and use
“Good enough” is not good enough for APIs that fuel
your business

4. Modern Serverless
Architectures- Scale by Design
Triggers
(response)
Actions
(functions)
Source
(events)
Results
Infrastructure as-a-service
• Multiple languages support
• Automatically scales
• Pay only for what you use
OpenWhisk- Open Source
partnership IBM & Apache
• IBM is leading contributor
• Foundation of IBM Cloud
Functions
© 2017 IBM Corporation
“This loosely coupled architecture makes OpenWhisk a
scalable, reliable, and robust serverless platform. Each
layer involved in the execution is designed to scale
independently.” The New Stack, An Architectural View of Apache
OpenWhisk, 3 Feb 2017, Janakiram MSV
Rules

5. 5
Missing Usage
Trails
Anonymous Access
Difficult to share
Fixed URL scheme
(no branding)
Serverless actions need securing and require ease…
© 2017 IBM Corporation

6. Define API
Endpoints (URLs)
(optionally by using custom
domains)
Define Actions:
Map Endpoints to
ActionsAPI Gateway takes care of:
Securing and Controlling your Serverless Action…
© 2017 IBM Corporation

7. And are Flexible
Any
Cloud
Any form-factor Microservic
eYou need to position your
gateway WITH your
microservices, no matter where
they are located
Your API Gateway needs to be
ready to be deployed in the
native form factor of the
microservices, to keep your Ops
and Gateway team sane
Your API solution needs to be a
microservice based solution, to
live between on-prem and
clouds with ease.
© 2017 IBM Corporation

8. Microservices application
Importance of API management
for microservices
API Gateway
Developer
Portal
API
Manager
API Gateway:
• Decoupling/routing
• Traffic management
• Security
• Translation
Developer portal:
• API discovery
• Self subscription/administration
• Account usage analytics
• Monetization
API Manager:
• Plan/product design
• Policy administration
• API plan usage analytics
• API Governance
© 2017 IBM Corporation

9. Integrating API Tooling with
Cloud Solutions…
Simple Rate Limiting
Rate Limit by Key
Quick Security
OAUTH (Social authentication),
API Key, CORS (basic)
Fast Socialization
Easy to create and share keys
Share instantly with
Analytics
Basic Debugging Logs
High Level Analytics
Integrated User
Experience
Natively (baked-in) with Serverless
and traditional apps
Scalable
Grows as your organization’s
API usage grows
© 2017 IBM Corporation

10. Microservice
component
Inter-microservice vs. inter-
application communication
Microservices
application
Microservice
component
Microservice
component
Inter-microservice communication
• Lightweight protocols: HTTP,
application messaging
• Runtime component registry
• Client-side load balancing and circuit
breaker patterns
Microservices
application
Exposure Gateway
Inter-application communication
• Enterprise protocols: Managed API
gateways, enterprise messaging
• Design time developer portals
• Gateway load balancing and throttling
JSON/HTTP RESTful communication styles may
be present in both types of communication, but
their implementation may be radically different.
JSON/HTTP
© 2017 IBM Corporation

11. Microservice
component
Containers: ISTIO –
microservices management
Inter-service proxy between microservices
(ie polygot runtimes)
– Non-intrusive to App (ie transparently
intercepted and proxied)
Inject app-smarts (ie rate limit, security, etc
…) in the network without making app
changes
Pluggable decision maker called mixer
optimized for inter-service communication
for enforcing
Microservices
application
Microservice
component
Microservice
component
Microservices
application
Exposure Gateway
JSON/HTTP
ISTIO ISTIO
© 2017 IBM Corporation
Open-source Partnership with IBM, Google and Lyft

12. Serverless APIs in under 30 seconds! Fastest on the cloud…
1. RESTful
App or Action
2. Select API
control and
security
3. Share API
keys and
documentation
30 Seconds on Bluemix
© 2017 IBM Corporation
https://console.bluemix.net/openwhisk/

13. The future of APIs is Cloud Native
regardless of where you start
Autoscalablity
Simplifies backend management
Simplifies Dev Ops
Cheaper
Reduce Vendor Lock-in
© 2017 IBM Corporation

14. IBM can Help You Modernize Your
Microservices and API Program
Help yourself
Developer Resources
developer.ibm.com/apiconnect
Try OpenWhisk on Bluemix (2M free) –
https://console.bluemix.net/openwhisk/
OpenWhisk Apache Project –
https://openwhisk.incubator.apache.org/
Try API Connect (Free) –
https://developer.ibm.com/apiconnect/getting-started/
DataPower on Docker (Free for devs) –
https://hub.docker.com/r/ibmcom/datapower/
Get our help
API Economy Discovery and Planning Workshop-
AP104
https://tepzone.tivlab.austin.ibm.com/services/offer
ing/show/6
AP108 API Economy Digital Transformation
https://tepzone.tivlab.austin.ibm.com/services/offer
ing/show/210
© 2017 IBM Corporation

15. 15© 2017 IBM Corporation
Thank you
Ken Parmelee
API Connect and Gateways Leader
—