[WSO2 Summit Sydney 2019] Building a Successful API Strategy from Scratch and Winning it
3 likes•504 views
The Integration Summit 2019 presented an API strategy that highlights the essential role of APIs in enabling digital enterprises and expanding revenue channels. Key steps in developing an API strategy include discovering data, understanding consumer channels, and implementing a comprehensive API lifecycle. The discussions emphasized the importance of managed APIs, security measures, and the establishment of an API marketplace to enhance adoption and streamline operations.
[WSO2 Summit Sydney 2019] Building a Successful API Strategy from Scratch and Winning it
- 1. INTEGRATION SUMMIT 2019 Building a successful API Strategy from scratch and winning it Vidura Gamini Abhaya Senior Director - Solutions Architecture INTEGRATION
- 2. API strategy : Why ? 2 ● APIs are the key enabler for a digital enterprise ● They are the fundamental building blocks of integration ● Increased adoption of APIs ● API’s ability to open new revenue channels and expand existing revenue streams. ● Necessity in understanding the APIs as an ecosystem rather than individual blocks. ● Alignment with the organization business goals.
- 3. An API Strategy 3 Steps in building an API Strategy: ● Discover data and capabilities to be exposed ● Discover channels (consumers) ● Introduce an API lifecycle ● Securing APIs ● Managed APIs ● API Marketplace ● Operational and Business Intelligence
- 4. Discover : Data and capabilities
- 5. What do you have in your Organisation? 5 ● Discovering the ecosystems and silos ● Understanding data ● Understanding capabilities ● Understanding engineering organisational behaviour ● Understanding engineering process ● Need of a unified governing process ● Changes to existing processes
- 6. Advocate API first design 6 Code first design API first design
- 7. API Façade 7
- 9. Discovering Consumer Landscape 9 ● APIs are a consumable product ● APIs can be consumed by parties which have different consumption models. ● API’s should be able to provide an omni channel experience.
- 10. API’s being used to .. 10 ● Providing superior digital experience ● Expand market channels and revenue streams ● Launching innovative products and services
- 11. Channel Definition 11 ● Define channels need to be supported
- 12. Interaction Definition 12 ● Request response models ● Fire and forget / Notification {from business point of view} ● Ping / knock
- 13. Usage Definition 13 ● Define SLA’s ● Handling business errors ● Handling operational errors
- 15. Richer API Lifecycle Management Experience 15 ● API - A first class product ● Provide a richer life cycle and its stages ● Define multiple state transitions between API states ● Supporting dynamic state transitions ● Ability to automate state transitions based on policies. ● Role based access control on lifecycle stages
- 16. WSO2 API Manager Standard API Lifecycle 16
- 17. Complex State Transition Use Case 17
- 18. Binding Event Notification to State Transition 18
- 19. Governance of lifcycle stages 19
- 20. Secure APIs
- 21. API Security Concepts 21 ● Secure API design ● API security is multifaceted ● Need to evolve and extend
- 23. API Security mapped to an incoming request 23
- 24. Channel specific security models 24 ● OAuth 2.0 Grant types based on channel
- 25. Managed APIs
- 26. What is a Managed API? 26 ● A managed API has a well-defined interface, a defined target audience, it is under appropriately enforced business and IT control and insight available of the usage.
- 28. Definition of a Managed API 28
- 29. Importance of Managed APIs 29 ● Improves software development efficiency. ● Operational and business analytics provide better developer and consumer experience. ● Faster delivery of digital assets. ● Compliance with standards.
- 30. API Marketplace
- 31. What API Marketplace Brings ... 31 ● Discovery of APIs by consumers ● Promote API reuse and adoption ● Provides a Social media experience ● Provides rendezvous point for API consumers and developers ● Provides tools, documentation, incentives such as monetization and supporting activities like evangelism, workshops, and hackathons.
- 32. API Marketplace Ecosystem 32 An Enterprise API Marketplace connects Producers with Consumers through a Technology Platform and related Activities
- 34. The API Marketplace Digital Experience 34
- 36. The Intelligent API Model 36 Usage prediction Security Model
- 37. Data Driven Risk Models 37 Data-driven risk models that monitor API calls will identify, ● Transaction anomalies ● Uncover hidden bot patterns and attacks ● Insights for counter measures and investigation support Powered by machine learning algorithms and predictive analytics to continually adapt to threats.
- 38. API and Big Data Patterns 38 Big Data as API Enabler ● Monitor and Control ● Billing and Metering ● API Store : Targeted Marketing ● Deployment Optimization ● Governance APIs as a Big Data Enabler ● Exposing Data Silos ● Controlled delegation of Data ● Data marketplace
- 39. Intelligence as an API 39 Through intelligence gathered from “unstructured data”, the massive amount of data resulting from API processing, patterns, relationships, and interactions between API datasets we open it as a service through API.
- 40. Components of WSO2 API Manager 40
- 41. INTEGRATION SUMMIT 2019 THANK YOU wso2.com