[WSO2 Integration Summit Singapore 2019] Transforming Your Business through APIs

INTEGRATION SUMMIT 2019
Transforming Your Business via APIs
Nadeesha Gamage
Senior Technical Lead @ WSO2
INTEGRATION

Important Facts About APIs
APIs now account for 25% of the Internet’s trafﬁc.
$1 trillion is up for grabs through the redistribution of
revenue through APIs (McKinsey 2017).
25% of revenue ﬂows through APIs (Vanson Bourne 2018).

Disaggregated Architectures Enable Better
Connectivity via APIs
CONSUMER DEMAND
SUPPLIERS DISAGGREGATE ARCHITECTURE TO MEET DEMAND
1
10
102
103
105
109
MONOLITHIC
BUSINESS APP
ENTERPRISE
APPS
DEPARTMENTAL
APPS
SAAS APPS
PUBLIC /
PRIVATE APIS
SERVERLESS &
MICROSERVICES
1970s
|
MAINFRAME
1980s
|
IT
AWAKENING
1990s
|
INTERNET
2000s
|
MOBILE
2010s
|
IoT/AI
2020+
|
DIGITAL NATIVE
4

Third-party
Apps
Mobile
B2B
Cloud Apps
Web Portal
API
Company Assets
& Services
API
API
API

Why APIs?

● A channel to expose information to a wide variety of
customers in an effective manner.
● A standard way to communicate between apps, data,
and services.
● Build tailored customer experiences on top of business
assets to improve the overall customer experience.
Why APIs?

● Explosion in the number of connected devices.
● Integrating the value chain. Integration with partners,
suppliers, etc.
● Rise of consumers who are empowered by technology.
Demanding more from businesses.
Your audience will probably be much bigger than you
think it is.
What Drives the Need for APIs?

It’s no longer about companies owning a particular asset.
It's about how the asset can be made available to
consumers, when, where, and how they want it.
What Drives the Need for APIs?

● Provides opportunities to scale the business without
physically expanding.
● Reach customer segments who are unreachable
through existing channels.
● Enable indirect sales via third-party apps.
APIs as a Business Channel

APIs: The Cornerstone of
Business Platforms

The Role of APIs in Building Business Platforms

Platforms
Provide a
Network
Effect

Do APIs Solve Everything?

● How APIs can be exposed in a standard way that can easily be
used by different parties?
● How to securely expose APIs to external consumers?
● How can the usage be tracked and monetized?
● How can you make the adoption processes shorter for your
API consumers?
● How can internal stakeholders easily publish and manage
APIs?
Business Concerns

● How can we protect internal assets to ensure only
authorized persons have access?
● How can we push changes to APIs without impacting
consumers who are using them?
● How can we make APIs reliable?
● How can we scale APIs as usage increases?
Technical Concerns

What’s the Solution?

API Management

● Exposing all APIs through a central gateway.
● Enforcing access control via this gateway.
● Easy to design and publish APIs for API developers.
● Easy to discover, tryout, and use APIs.
● Provide reliability, high availability, and backward
compatibility for APIs.
● Understand usage, trends, and monetize APIs.
API Management

WSO2’s API Management Solution

● How to ensure APIs are not accessed in an ad hoc
manner.
● How to ensure APIs are accessed only by authorized
users.
● How to ensure your APIs are not exploited or
overused.
API Security

● All API requests come in via the API Gateway.
● The API Gateway becomes the Policy Enforcement Point for
APIs.
● Backend services can delegate authentication and authorization
to the API Gateway.
API Security - Single Point of Entry

API Security - Single Point of Entry

● Authentication and Authorization via OAuth 2.0 and
JWT.
● Authorization to APIs and resources based on user
roles.
● Extensibility with an XACML entitlement server for
attribute-based authorization.
API Security - Authentication and Authorization

API Security - Authentication and Authorization

● Usage control based on a subscription.
● Multiple levels of subscription with different usage plans.
● Throttling and burst control to provide fair usage of APIs.
● Usage control based on the number of requests or bandwidth.
● Protect the backend against overuse.
API Security - Throttling and Rate Limiting

API Security - Throttling and Rate Limiting

● A portal to create, publish, and manage APIs.
● Create APIs from API docs (Swagger).
● API lifecycle management.
● Versioning of APIs to support backward compatibility.
● Admin APIs to programmatically publish and manage
APIs.
● API-ﬁrst development methodology.
Ease of Management

● A portal to discover APIs.
● Lists API deﬁnitions, related documentation, and usage
instructions.
● SDKs for easy integration with applications.
● The ability to try out APIs before adoption.
Easy Adoption

Easy Adoption - Developer Portal

● Make the system highly available and fault tolerant.
● Eliminate single point of failures.
● Flexibility to deploy on multiple deployment zones.
Availability and Reliability

Availability and Reliability

● Statistics available for both API consumers and
publishers.
● Understand the usage patterns of your APIs.
● Monitor service availability and trigger alerts.
● Monetize the API usage.
Monitor and Monetize

Monitor and Monetize

Case Study

Integrated Logistics Platform via APIs

THANK YOU
wso2.com

[WSO2 Integration Summit Singapore 2019] Transforming Your Business through APIs

More Related Content

What's hot (20)

Similar to [WSO2 Integration Summit Singapore 2019] Transforming Your Business through APIs (20)

More from WSO2 (20)

Recently uploaded (20)

[WSO2 Integration Summit Singapore 2019] Transforming Your Business through APIs