View
187
Download
0
Category
Tags:
Preview:
Citation preview
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?
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
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
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)
Collect StaRsRcs, Analyze & Improve
• Put in place systems for collecRng staRsRcs • API Usage can explode -‐> More staRsRcs • Scalable StaRsRcs storage
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
Provide Tooling for Developer
• Trying out APIs • CreaRng Test Plans • Status Dashboard • Data APIs • Provide an ApplicaRon Development Plakorm
Recommended