Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

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


Published on

This deck explores how businesses can gain from APIs and the process of creating an API Marketplace.

Published in: Technology
  • After many failed attempts, I almost packed in my GCSE maths altogether. But fortunately I didn't, thanks to Jeevan's guide! When I read it, I found out exactly where I was going wrong all this time! I followed his approach and achieved 90% in my next sitting. I was shocked and I thought it was a total fluke so I put his strategy to the test again. This time, I got 100%! Fantastic! If only I came across Jeevan's strategy sooner. Learn more.. ■■■
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

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

  1. 1. Senior Solutions Engineer, WSO2 Transforming your Business through APIs Mauro Niewolski
  2. 2. As we spend more time on the mobile, the application economy will define how we do commerce
  3. 3. Behind every successful app is an API
  4. 4. APIs always come first
  5. 5. 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
  6. 6. Cleaning your house before guests arrive
  7. 7. 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
  8. 8. 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 ?
  9. 9. 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
  10. 10. Following the rules of economics
  11. 11. 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
  12. 12. Transparency ● Observability events ○ Where integrators can trap them and handle ● Feedback data ○ API consumption patterns ○ Availability data ● Troubleshooting data ○ Error codes / meaningful messages
  13. 13. Participation ● 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
  14. 14. Room for personalization ● API composition at the edge ● Letting the consumer decide how they want to consume API Platform (Shared Features) API /foo API /bar App A API /bar App B
  15. 15. APIs hold the key to Digital Transformation 16 Build internal and external developer ecosystems with an API marketplace
  16. 16. 17 Why Open Source API Management? ● Business friendliness: Apache 2 Open source ● Readability of code: Ease of extension and customization ● Open source (not open core) ● Platform lock-in implications ● Vendor lock-in implications ● Strength of the OS community ● Level of commercial support: Reliability, low cost trials/POCs ● OS governance model
  17. 17. WSO2 API Manager
  18. 18. API Publisher ● Design, mock and document REST and SOAP APIs. ● Create new versions of APIs ● Gain API usage insights for operational purposes ● Import API definitions ● Apply policies for security, rate limits and message transformations. The Portal for API Designers and Product Managers. ● Validate and publish APIs for public discovery and consumption. ● The central point for managing the API’s Lifecycle. ● Monetize APIs through business plans. ● Gain API usage insights for business purposes. Designers Product Managers
  19. 19. 20 ● Start with an existing endpoint/ contract or design and prototype a new API ● Exposing SOAP services (convert to REST or as a passthrough) ● Exposing streaming APIs (Websocket endpoints) Creating APIs
  20. 20. 21 ● API Design - Over the wizard & with swagger Creating APIs
  21. 21. 22 ● Point to a production backend or prototype at the gateway Managed or prototyped
  22. 22. 23 ● Manage stages of an API ● Manage associated states ● Create a new version from an existing ● Audit changes to lifecycle states ● Support for custom lifecycles API Lifecycle Management
  23. 23. Developer Portal The Application Developer Portal known as the API Store. ● Discover, test and subscribe to APIs ● Search through APIs and their documentation ● Rate, comment and participate on discussion forums of the portal ● Try out the API SDKs for faster go-to-market of applications. ● Manage the lifecycle of applications across environments ● Integrate with third party authorization servers
  24. 24. 25 ● Try APIs directly The Developer Portal
  25. 25. Key Manager and Traffic Manager ● Scalable and flexible authentication and authorization policy enforcement based on OAuth2.0 and other protocols. ● Integration with third party authorization services ● Supports a wide range of application types such as mobile, web, SPA, wearable devices, biometrics, etc ● Social integration for login via social networks and other IDPs. ● Rate limits used for billing and metering purposes ● Fair usage policy enforcements ● Rate limits based on user privilege, location, device type, etc. ● Rate limits for target services Security Rate Limiting
  26. 26. Wrapping it up
  27. 27. “It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change.” Charles Darwin
  28. 28. Customers
  29. 29. THANK YOU