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.

How to use Donuts and Onions for Scaling API Programs

7,097 views

Published on

Talk at APIStrat Chicago, September 25 about scaling API programs particularly about API adoption, operations, and analytics.

The talk was also recorded. Unfortunately the first couple of minutes were cut. You can find the video also here:
https://www.youtube.com/watch?v=PXmAemMqyME

Published in: Technology
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

How to use Donuts and Onions for Scaling API Programs

  1. 1. How to use Donuts and Onions for Scaling API Programs
  2. 2. How to use Donuts and Onions for Scaling API Programs @ManfredBo Manfred Bortenschlager I work at 3scale.net Out-of-the-box API Management @3scale APIStrat Chicago September 25, 2014 @API_Mag
  3. 3. What do I want to achieve? Share best-practices related to scaling API programs 3 @ManfredBo  API Adoption  API Operations  API Analytics
  4. 4. Operations 4 @ManfredBo
  5. 5. Operations 5 @ManfredBo
  6. 6. Objective of an API Program To increase quantity and/or quality of API adoption. 6 @ManfredBo
  7. 7. Because Developers are People, too 7 @ManfredBo DX – Image source: http://dx.jeremiahlee.com/
  8. 8. A developer program is the manifestation of DX. 9 @ManfredBo Ideally.
  9. 9. Developer Portal Acceleration Pilots / Case Studies Community Building Measure Comms Social Media Events Evangelist
  10. 10. Image Source: http://exclusiveblend.files.wordpress.com
  11. 11. 12 @ManfredBo
  12. 12. Operations 13 @ManfredBo
  13. 13. Minimum API Operations Access Control: authentication and authorization to identify the originator of incoming traffic and ensure only permitted access. Rate Limits and Usage Policies: usage quotas and restrictions on incoming traffic to keep loads predictable. Analytics: data capture and analysis of traffic patterns to learn how the API is being used. 15 @ManfredBo
  14. 14. Cost Speed Dependability Internal Quality Flexibility External 16 @ManfredBo Source: Nigel Slack et al. (2013)
  15. 15. Cost Speed Dependability Internal Quality Flexibility 17 @ManfredBo Value for All 4 objectives money Perceived value External Rate limits Availability Versioning Releases DX Evangelists Documentation Support Caching Latency
  16. 16. Operations 18 @ManfredBo
  17. 17. Lean Analytics Source: Alistair Croll & Benjamin Yoskovitz (2013): Lean Analytics 19 @ManfredBo
  18. 18. 21 @ManfredBo
  19. 19. Metrics: • Number of API calls (per API per time unit) • Latency, availability, round trip • Response/error types • Activities of apps/developers • Etc. Make sure to measure the right things in the right stages. 22 @ManfredBo
  20. 20. New ebook “Building Effective API Programs” Get it from http://www.3scale.net/blog/ Or contact manfred@3scale.net 26 @ManfredBo
  21. 21. APIStrat Speed Hack Friday, Sept. 26 11:45am Developer Track 27 @ManfredBo
  22. 22. Wrap-up & Take-away A scaling API program requires a lot more than a technically well-working API. API adoption in quantity or quality is mandatory. DX is the key to adoption. Evangelists are key to DX. The API operations’ key performance objectives are designed to support adoption. API Analytics give you the intelligence to steer. 28 @ManfredBo
  23. 23. How to use Donuts and Onions @ManfredBo Q&A Manfred Bortenschlager I work at 3scale.net Out-of-the-box API Management @3scale for Scaling API Programs

×