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.

Adopt an API Product Mindset

5,775 views

Published on

Delivering API products instead API projects requires a mindset shift. Teams must understand client business goals, promote a cohesive API product portfolio, and efficiently evolve the API. To deliver and evolve successful APIs, build an API strategy incorporating digital business best practices and agile architecture. In this session, Chris Haddad will describe:

Why API design influences API adoption

How to avoid the new today, legacy tomorrow API trap

Where API governance and lifecycle management intersects with SOA governance

Published in: Technology
  • Be the first to comment

Adopt an API Product Mindset

  1. 1. Adopt a SuccessfulAPI Product Mindset Chris Haddad @cobiacomm on Twitter http://blog.cobia.net/cobiacomm Read more about WSO2 API Manager at http://wso2.com/products/api-manager
  2. 2. API Product Success• Reach – Number of Consumers – Data and Transaction Breadth• Impact – Aggregate Usage – Usage per Consumer• Revenue – Direct and Indirect Revenue – Operating Margin / Net Margin
  3. 3. API Product Failure• Delivery issues – Capacity Melt-down – Server Error 500 , 404, 429• Challenging interfaces and integration – Complicated URLs and Requiring Payloads – Authentication Token failure• Evolution and monetization hurdles – Anonymous Users – Ambiguous and shifting business models – Minimal adoption
  4. 4. Product Mindset Facets API Evolution API APIEngineering Promotion API DeliveryAPI Design API Monetization API Terms of Service
  5. 5. API Product Mindset Markers• Understand your business model• Expose a business capability as an API product• Socialize availability• Encourage ecosystem adoption and API composition• Evolve and scale the API• Loop and re-examine the business model
  6. 6. Product Mindset Mojo• Warranty – Quality of Service – Scale – Longevity• Packaging – Well-defined focus – Tiered Service Levels – Contextualization• Evolution, adaptability, and agility – Minimal Viable Product – Less is more – Versions are a big, non-trivial event• A business model
  7. 7. Evolution, Adaptation, Agility
  8. 8. API Product Governance• Manage Dependencies• Track adoption – Usage and Subscription Tracking• Manage Compatibility – Backwards or Forwards – Versioning• Communicate Migration Strategies – Deprecation, Retirement
  9. 9. The Whole Product ViewDependencies and Technologies under the surface• Apps are the delivery mechanism• APIs are the external core interfaces• Services are the internal implementation• Processes define business differentiation• Data has gravity – Cache is persistence, Database is a repository Composition is orthogonal and important
  10. 10. Very Large API = Increase API Reach Description Context Personalization
  11. 11. Situational Context
  12. 12. Micro-Context Dimensions Consumer’s Intent • Goals, Interests, and Objectives • Requirements and constraints • Available Resources – Human, physical, financial
  13. 13. Micro-context and the Long Tail Drives the Pull EconomyChart Credit: http://keithhopper.com/blog/long-tail-consumer-demand
  14. 14. Common API Personalization Dimensions• Information access privileges• Information aggregation and composition• Social network access privileges• Business processes and rules• Service levels and Quality of Service• Security policies• Monetization rates
  15. 15. Questions?

×