Adopt an API Product Mindset
•Télécharger en tant que PPTX, PDF•
4 j'aime•5,512 vues
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
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (20)
Plus de Chris Haddad
Plus de Chris Haddad (20)
Dernier
Dernier (20)
Adopt an API Product Mindset
- 1. Adopt a Successful API 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. 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. 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. Product Mindset Facets API Evolution API API Engineering Promotion API Delivery API Design API Monetization API Terms of Service
- 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. 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
- 8. API Product Governance • Manage Dependencies • Track adoption – Usage and Subscription Tracking • Manage Compatibility – Backwards or Forwards – Versioning • Communicate Migration Strategies – Deprecation, Retirement
- 9. The Whole Product View Dependencies 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. Very Large API = Increase API Reach Description Context Personalization
- 12. Micro-Context Dimensions Consumer’s Intent • Goals, Interests, and Objectives • Requirements and constraints • Available Resources – Human, physical, financial
- 13. Micro-context and the Long Tail Drives the Pull Economy Chart Credit: http://keithhopper.com/blog/long-tail-consumer-demand
- 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. Questions?
Notes de l'éditeur
- Adopt a Successful API Product Mindset [ minutes]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 adoptionHow to avoid the new today, legacy tomorrow API trapWhere API governance and lifecycle management intersects with SOA governance
- understand client business goals, promote a cohesive API product portfolio, and efficiently evolve the API
- Wrap up….
- build an API strategy incorporating digital business best practices and agile architectureunderstand client business goals, promote a cohesive API product portfolio, and efficiently evolve the APIVersioning Strategies:https://groups.google.com/forum/?fromgroups#!topic/api-craft/iInGY4vmgroVERSION DATA formats --
- Apps are the delivery mechanismAPIs are the external interfaceServices are the internal implementationProcesses define business differentiationData has gravity
- In astronomy, VLA stands for Very Large Array. Very Large Arrays are used to map the universe. You can extend your API’s reach by carefully crafting API descriptions, augmenting API context, and embedding personalization.
- -----Source: http://www.starwoodhotels.com/westin/property/area/map.html?propertyID=3789&language=en_USBrowser Demo calling back into MapQuest Location APIhttp://developer.mapquest.com/content/documentation/sdk/js/v7.0/samples/controls_geolocation_jquery_try.htmlReal-time traffic map: http://www.mapquestapi.com/traffic/
- Micro-context dimensions adapt the Web to an individual person or organization.Consider adapting your API based on consumer goals, interests, objectives; requirements and constraints; or available consumer resources. For example, the consumers manpower, physical tools, or financial position. The micro-context of a vacationer’s request in New York City is very different from a request posted from a remote beach in the Bahamas.
- four macro context items: location, visual cues, traffic, and weather.Micro-context tailors information delivery based on specific individual wants, needs, and capacity. APIs may be one-size-fit all and focus on popular demand, or tailored to enable the long tail. Context drives a pull economy, where API consumers can find and access a custom designed API. Instead of API providers specifying API response, API consumers drive interactions and content. -----Image Source: http://keithhopper.com/blog/long-tail-consumer-demand
- API behavior and responses can be personalized per caller. Common API Personalization Dimensions include:Information access privilegesInformation aggregation and compositionSocial network access privilegesBusiness processes and rulesService levels and Quality of ServiceSecurity policiesMonetization ratesHow many of these are built into your API?