API Management and Community Development layer 7 in london 2012


Published on

Businesses are increasingly considering API-driven business strategies. What works in API management and how does it underpin Developer Experience?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Mike Stonebreaker, founder of seven different database companies, told the GlueCon audience in 2010 that it was impossible to be a new project in the database space without being open source.
  • W hat does this mean for systems of record/systems of engagement ….
  • API Management and Community Development layer 7 in london 2012

    1. 1. API Management and Developer Outreach: Learning from the Web 10.20.2005Layer 7 London 25th September 2012
    2. 2. Software is Eating the World 2
    3. 3. Software in the 20th Century 3
    4. 4. Software in the 21st Century 4
    5. 5. The Developer Strikes Back 5
    6. 6. New Kingmakers 6
    7. 7. API protocols and styles 7 ProgrammableWeb, February 2012
    8. 8. Rise of the APIs 8
    9. 9. Rise of the API Giants 9
    10. 10. Fragmentation of Everything 10
    11. 11. Explosion of Forms 11
    12. 12. Language Tiers 12
    13. 13. Purchasing First“Operating systems, databases, web and application servers, dev toolsall required money. To get anything done, then, developers neededsomeone to write checks for the tools they needed to build. Thatmeant either raising the capital to buy the necessary pieces, or moreoften requesting that an employer or other third party purchase themon the developers behalf.” Stephen O’Grady – New Kingmakers 13
    14. 14. No Permission Required S 14
    15. 15. Encourage Foragers 15
    16. 16. Foraging For Code 16
    17. 17. Design• Good APIs generate great PR - early adopters as evangelists• Bad APIs generate a ton of calls to your support organisation• REST not SOAP (and definitely not WS-*)• JSON not XML• API first design encourages service modularity, enabling reuse • Cloud First (with onprem in mind) • Social First (with enterprise in mind) • Mobile First (with desktop in mind)• Easy to Learn, Easy to Use, Easy to Extend• Minimum Progress to Declare Victory. Avoid “Requirement Creep” 17
    18. 18. DevOps and Continuous Integration 18
    19. 19. Engage• APIs don’t build communities, people build communities• The API Economy is a social phenomenon• APIs are a contract• Community management is not optional – invest in people• Your people may already be good at this• Good APIs make hiring easier• Web APIs set the bar for consumability• A VC Fund for your API 19
    20. 20. $250k $1m $1m $2m20
    21. 21. Then Forge 21
    22. 22. API Management – The New SOA• Authentication and authorisation• Billing• Browsing and discovery• Certificates• Documentation• Interface Conversion (SOAP to REST, XML TO JSON)• IP addresses• Publishing• Portal• Testing• Throttling 22
    23. 23. Turn Legacy into New Products“The lumber industry sells what used to be waste — sawdust, chips, and shredded wood — for a pretty profit. Today you’ll find these by-products in synthetic fireplace logs, concrete, mulch, particle board, fuel, livestock and pet bedding, winter road traction, weed killing and more.” Jason Fried, 37signals 23
    24. 24. • Activity Streams• Customer service feedback• Influence patterns – internal and external• Location, location, location• Operational data - maintenance• Search Logging – for prediction• Sentiment• Transactional (meta) Data 24
    25. 25. APIs: Now a Billion $ Business = $2 billion/year Affiliate Network “90% of what we do is business through APIs” John Watton, Expedia Affiliate Network, Travolution.co.uk, April 2012 25
    26. 26. Social, Local, Mobile Facebook: 1bn monthly active users 500m+ are mobile 30 Petabyte+ Hadoop cluster Foursquare: 3m Check-Ins Per Day 500k Merchants Twitter: 340 million tweets per day 24m – Lady Gaga’s followers 26
    27. 27. Transactions in the Age of Engagement 27
    28. 28. Afraid of Downtime? 28
    29. 29. Recommendations and Wrap UpAPI-First developmentDeveloper Experience marries social and technicalDocumentation is a developer funnelInvest in DesignInvest in Developer Relations and Developer ExperienceInvest in solid tooling, designed to support peopleOpen Source contributions foster community goodwillMake future API plans clear from the outset, where possibleOptimise for Happiness – for internal and external developers 29
    30. 30. Optimise for Happiness37SignalsEtsyGithubHow To Design A Good API and Why It Matters, Joshua Block 30
    31. 31. CreditsPhotos:SF in Cloud – SF ChronicleCraftsman – A. Davey on FlickrBarbed Wire by tacitrequiem on FlickrVC chart data from the National Venture Capital Association and the Center for Venture Research, via @cbtacy from AppFog 31