We live in a world where many digital services are offered as APIs today. You will find APIs for finance, healthcare, communication, retail, travel and transportation, leisure, real estate, and many more services. These APIs form a large global ecosystem of APIs providing great value for new digital services. For businesses to be able to participate in this ecosystem, they have to be providing their services through the Cloud, in the form of APIs. This workshop discusses what developers should be thinking about when developing and exposing new APIs on the cloud. It will also cover best practices, pitfalls, and security-related matters that will be important for developers and architects who are building APIs on the cloud.

1. Programming the cloud through
APIs

2. Hello!
Nuwan Dias
2
VP and deputy CTO - WSO2
Co-author, Microservices Security In Action
@nuwandias

3. 3

4. 4

5. Growth of the cloud market
5

6. Growth of the cloud market
6

7. 7
Source:
https://www.bvp.com/atlas/stat
e-of-the-cloud-2020/

8. With APIs, your time to market goes down from
months to days!
8

9. Setting up a greeting-card business
2000
● Rent a Garage.
● Buy server equipment.
● Figure out how to make online
payments.
● Write greeting-card generation
software.
● Hire people for printing and
mailing.
9
Today
● Nah! I’ll WFH.
● Rent computing from an IaaS
provider.
●
● Write greeting-card generation
software.
●
Credit: https://www.swyx.io/api-economy/

10. Building software in a cloud native world
● Any software you build today will have to integrate with many APIs.
● Integrating with an API means two things.
๏ Connecting to the API.
๏ Programming with the API.
● Getting an API to work requires,
๏ Development of the API.
๏ Testing.
๏ Deploying into production.
๏ Exposing for consumption.
๏ Observing the API for performance and troubleshooting.
๏ Obtaining insights to plan future work and iterate.
10

11. Developing an API
Developing an API requires,
● Writing code.
● Discovering dependant APIs.
● Connecting to dependant APIs.
๏ Passing credentials securely.
● Learning how to use APIs through their
documentation.
● Data manipulation.
● Data mapping.
11

12. Testing an API
Testing an API requires,
● Trying it out.
● Running Unit tests.
● Running Integration tests.
12

13. Deploying an API to
production
A production deployment is a big task. It requires,
● GitOps.
● DevOps.
● CI/CD pipelines.
● Secure credential transferring.
● Blue/Green, Canary or other similar
deployment strategies.
● Reliability
๏ Auto-scaling.
๏ Auto-healing.
13

14. Exposing an API to
consumers
Once an API is running, managing its exposure
becomes critical. This requires setting up,
● API governance.
๏ Lifecycle management.
๏ Documentation.
๏ Usage plans.
● API security.
๏ Authentication.
๏ Authorization.
๏ Access control.
● Developer portal.
๏ Developer sign-ups and workflows
๏ AIP Docs.
๏ SDKs.
14

15. Observing an API
In the cloud-native world, monitoring an API
requires,
● Monitoring third party APIs your API may
rely on for performance, availability and
errors.
● API performance, availability and errors.
● Resource utilization.
● Logs.
15

16. Obtaining insights for
business
Business insights can be useful for,
● Projecting business growth.
● Estimating customer NPS through,
๏ API latencies.
๏ Error rates.
๏ Churn rates.
● API lifecycle management.
● Product roadmap decisions.
16

17. Demo Time!
17

18. Questions
18

19. A Next-Generation
Integration Platform as a Service
for Cloud Native Engineering
Thanks!
wso2.com/choreo
https://twitter.com/ChoreoDev
19