[WSO2Con USA 2018] API Marketplaces - The Enterprise Version
1 like244 views
The document discusses the importance of APIs in the mobile application economy, emphasizing that a successful app relies on efficient API integration and agile management. It outlines the strengths, weaknesses, opportunities, and threats of enterprise API marketplaces, advocating for a team-based approach to API product development and governance. Real-world examples illustrate how companies like BNY Mellon and StubHub leverage APIs for digital transformation and operational efficiency.
![[WSO2Con USA 2018] API Marketplaces - The Enterprise Version](https://image.slidesharecdn.com/apimarketplacestheenterpriseversionus18-180718065418/85/WSO2Con-USA-2018-API-Marketplaces-The-Enterprise-Version-3-320.jpg)
[WSO2Con USA 2018] API Marketplaces - The Enterprise Version
- 1. Dir. Solutions Architecture API Marketplaces - The Enterprise Version Nuwan Bandara @nuwanbando
- 2. As we humans spend more time on the mobile, the application economy will define how we do commerce
- 4. It’s bigger than Hollywood http://www.businessinsider.com/app-industry-hollywood-comparis on-2015-1
- 5. Behind every successful app is an API
- 6. API always comes first
- 7. API economy is not about monetizing the API ● It’s about speed to market ● Knowing the unknown ● Experiment with the economics ● Changing the human behavior Source: David Sacks, Yammer on Uber’s business model valuation
- 8. Cleaning your house before guests arrive
- 9. Don’t give me a file; give me an API ● Siloed business unit operations ● Repetitive digital initiatives ● Decades old cross BU integrations ○ FIle drops ○ Batch based sync jobs ● Years of technical debt
- 10. Innovation is driven by agility ● Startups are winning the app economy ○ Greenfield technology ○ Small teams, focused scope ● The feedback loop disconnects within a siloed enterprise Fun fact: Who would have thought we will get a home loan through a mobile app ?
- 11. Enterprise API Marketplace SWOT Strengths Weaknesses Opportunities Threats Domain specific / Specialized BUs Technical debt Every BU contribute to the investment and cost of operation Over governance of APIs Clearcut process ownership Initial time investment and re-engineering Potential new business opportunities outside the enterprise Huge re-engineering costs for API enablement - with waterfall type scopes Each unit has its own IT/digital enablement team Greater agility and productivity in resource and information sharing Over engineering the API gateway technologies and use cases Feedback loop low entry barrier for application development
- 12. Two-Pizza team rule ● An API product is done by a Two-Pizza team ● Team owns end to end ○ Write the code and implement the business function ○ Test and automate ○ Push towards the pipeline ○ Deploy, orchestrate and chaos test ○ Observe ○ Iterate WSO2 White Papers, Reference methodology for agility, by Asanka Abeysinghe, Dr. Paul Fremantle The integration agile team
- 13. A reference implementation External Developers (Partners) Other BU Developers (Inter BU Access) Internal BU Developers (Intra BU Access) BU 1 API Marketplace BU 2 API Marketplace BU 3 API Marketplace BU n API Marketplace BU 1 API Management (Dedicated On-prem Deployment) BU 2 API Management (Private Cloud Tenant) BU 3 API Management (WSO2 API Cloud Tenant) BU n API Management (Other APIM Platform Tenant) Private Cloud Public Cloud Enterprise Enterprise API Marketplace BU 1 BU 2 BU 3 BU n
- 14. Following the rules of economics
- 15. Market is the only means of trade ● Incentives ○ API leaderboards ○ Inter-BU revenue sharing ● Hackathons and evangelism ● Reducing the entry barrier to consume APIs ○ API implementers can follow Postel’s law ○ Self service whenever possible ○ Tutorials / code-get type tools
- 16. Transparency ● Observability events ○ Where integrators can trap them and handle ● Feedback data ○ API consumption patterns ○ Availability data ● Troubleshooting data ○ Error codes / meaningful messages
- 17. Room for personalization ● API composition at the edge ● Letting the consumer decide how they want to consume API /bar
- 18. Participatory governance & governance by surveillance ● Letting the market decide what’s best and how best it can be used ○ Iterative changes / change requests / versions ● Transparency through observability ● Evolution through feedback ○ Ratings / comments ● Compliance through policy enforcement ○ GDPR / HIPPA / PSD2
- 20. BNY Mellon’s NEXEN digital ecosystem https://wso2.com/blogs/thesource/2016/03/wso2con-insights-how-wso2s-open-source-api-management-platfor m-is-enabling-bny-mellons-digital-transformation/
- 21. TFL Smart transportation grid https://wso2.com/blogs/thesource/2017/10/a-smarter-transport-management-system-for-london-with-the-help-of-wso2/
- 23. During this week
- 24. Building an enterprise API marketplace driven business platform Define API Strategy Define Technology Strategy Facilitate Consumers Engage and Empower Producers Evangelize Incentives Monetize and Analyze Govern and Manage