WSO2Con EU 2015: Towards a Winning API Strategy Today, every enterprise agrees that there is a pressing need for business APIs. However, it’s the right API strategy that will make business APIs a winning one. This session will explain how you could formulate a winning API strategy, and will particularly focus on the following areas: What are the key ingredients in defining a winning API strategy? How should the strategy be converted into a set of action items that will create a winning combination? How can WSO2’s API Management capabilities help? It will also touch on some real customer scenarios where WSO2′s platform has been a key part in implementing a winning API strategy for these enterprises. Presenter: Sumedha Rubasinghe Director – API Architecture, WSO2

1. Towards
a
Winning
API
Strategy
Sumedha
Rubasinghe
Director
–
API
Architecture,
WSO2

2. Lesson
#1:
Why
|
How
-­‐
APIs?

3. Why
&
How
–
API
Strategy
• Why
would
you
need
an
API?
• Public
|
Private
-­‐
API?
• API
as
a
Product
|
API
as
of
business
?
• Who
is
your
target
audience?

4. Lesson
#2
:
Define
Expected
Outcome

6. Lesson
#3:
APIs
are
only
front
facing.
Focus
on
IntegraRon.

7. Focus
on
IntegraRon
• APIs
expose
backend
funcRonality
• SOA
vs.
API
• API
should
connect
to
exisRng
User
Management
Systems
– Eco
System
• API
Developer,
API
Consumer
(external
developer),
End
User
• MediaRon
–
API
Façade
PaZern

8. Lesson
#4:
AdverRse
Your
APIs

9. AdverRse
Your
APIs
• Applicable
to
Private
|
Public
APIs
• API
Portal
– Discoverable
– DescripRve
– Organized
– SubscripRon
Ready
– Trying
out
&
Tooling
• Create
moRvaRon
to
use
APIs
&
build
Apps

10. AdverRse
Your
APIs

11. AdverRse
Your
APIs

12. AdverRse
Your
APIs

13. Lesson
#5
:
Evolve

14. Keep
on
Improving
Your
APIs
• Step
1:
define
versioning
strategy
• End
users
interact
with
Apps
• Apps
use
APIs
• APIs
should
support
the
ever
demanding
interacRon/usage
paZerns
– Event
Driven
Programming
– LocaRon
based
Caching
• Evolve
with
feedback
from
developer
community
• Choose
correct
technology
(REST/SOAP,
XML/JSON)

17. Lesson
#6
:
Measure

20. Collect
StaRsRcs,
Analyze
&
Improve
• Put
in
place
systems
for
collecRng
staRsRcs
• API
Usage
can
explode
-­‐>
More
staRsRcs
• Scalable
StaRsRcs
storage

21. Lesson
#7
:
Protect
Your
APIs

22. Observe
Usage
PaZerns
&
Protect
• Measures
for
intruder
detecRon
– SQL
InjecRon
– JSON/XML
aZacks
• Plan
a
failing
strategy
• Extend/Control
with
workflows
– Eg:
who
can
subscribe,
generate
tokens,
publish
APIs

23. Lesson
#8
:
Provide
Tooling

24. Provide
Tooling
for
Developer
• Trying
out
APIs
• CreaRng
Test
Plans
• Status
Dashboard
• Data
APIs
• Provide
an
ApplicaRon
Development
Plakorm

25. Lesson
#9
:
OperaRon
Planning

26. Lesson
#10
:
Legal
ConsideraRons

27. How
WSO2
API
Management
Plakorm
can
help?

28. Complete
API
Management
Plakorm

29. Customizable
API
Store

30. Extensions
&
Workflow
Support

31. Scalable
StaRsRcs
Processing

32. VisualizaRon
Support

33. Support
for
ALM

34. Thank
You.