Trends in Web APIs Layer 7 API Management Workshop London


Published on

Learn about the major API management and design trends of today, tomorrow and the distant future in this tour of the API universe.

Published in: Technology, Design
1 Comment
  • Brilliant presentation!
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Today = things we can see happeningTomorrow = things we know are out thereThe Future = things that we can speculate about, may or may not happen
  • Timeline EventsEvent: API released (2000)Description: introduces an XML API (the SOAP API would follow shortly) that allows their customers to integrate on-premise systems with a cloud based CRM system.Significance: One of the earliest examples of what is now commonly referred to as a Web API and also an early indication of the need for SaaS providers to provide integration hooks in order to market their products to business customers.Event: eBay API released (2000)Description: eBay launches a developer program ( and API as a means to allow developers to integrate eBay functionality with websites and third party products. Joining the developer program requires developers to sign a license agreement and pay a fee.Significance: The eBay API is one of the earliest examples of an API designed to attract developers and is the pioneer for what we now consider to be a public Web API.Event: Amazon API released (2002)Description: Amazon releases the Amazon Web Services platform and spearheads the IaaS movement.Significance: Amazon (through a dictum from Jeff Bezos) had embraced the idea of web APIs for all internal services and was able to leverage this service based architecture to find a new stream of profit. AWS and it’s descendant EC2 are a great early example of using existing assets to find new revenue streams via APIs.Event: Flickr API released (2004)Description: Flickr a collobarative photo sharing site and web 2.0 pioneer releases a web API.Significance: Flickr was one of the first social and collaborative products to offer a web based API and was one of the first to use the API as an effective way of finding new partners and business streams. Organizations that wanted to partner with Flickr could easily use their API rather than broker out of band meetings with Flickr executives and there was a great focus on the collaborative spirit of web 2.0Event: First Web 2.0 Conference (2004)Description: O’Reilly (the book publisher) launches the first web 2.0 conferenceSignificance: Event: launched (2005)Description: Significance: Event: Description: Significance: Event: Description: Significance: TODO: Add technology shifts (e.g. OAuth 1, Oauth 2)Flicr API pay model.Add: Date that google drops their soap search API. (search engine land, dec. 2006)
  • API Growth is strong
  • Mobile is a key driver for APIs
  • Summary slide
  • Trends in Web APIs Layer 7 API Management Workshop London

    1. 1. Trends in Web APIsRonnie MitraPrincipal API Architect - EMEALayer 7 API Academy
    2. 2. The Layer 7 API AcademyMission: Ronnie Mitra Mike Amundsen To help API Publishers build great APIsMethod: Conference Presentations Books, Blogs, Tutorials and Tech Talks Workshops and Mentoring
    3. 3. API
    4. 4. int printf ( const char * format, ... );
    5. 5. Web API
    6. 6. Web API =Technology
    7. 7. Is it a Web API?REST/JSON? Yes. SOAP/XML? Yes. HTTP/CSV? Yes.
    8. 8. Design APIs for your users.Developer experience is Paramount.
    9. 9. API
    10. 10. TheFutureTomorrowToday
    11. 11. Today
    12. 12. Modern Timeline of Web APIs 2005 2004 2010 First Web 2.0 Programmable Salesforce Conference adds HTTP API launched 2002 54 APIs Amazon API registered. 20052000 ebay makes 2008 2012Salesforce API APIs free Programmableebay API Programmable has has 2004 2006 1000 registered 7144 registered Flickr API Twitter API APIs APIs Facebook API Google (Maps) Sources: API Steve Yegge Rant
    13. 13. The enterprise model:Start with private APIs…
    14. 14. …consider going public in the future
    15. 15. Mobile is driving API publishers
    16. 16. Bandwidth is a key constraint
    17. 17. HTTP-CRUD is the style of choice. GET PUT POST DELETE
    18. 18. Designers care about URI design /apple /apples /apples?colour=green /bushel/apples/
    19. 19. Security remains importantAPI standards have emerged
    20. 20. OAuth 2 is gaining popularity
    21. 21. Flexibility is the new challengeSAML PKI LDAP WS-*
    22. 22. API publishers are becoming API consumers
    23. 23. The primary API management challenge: Balancing Control and Accessibility
    24. 24. API publishers want to encourageutilization
    25. 25. Low barriers to accessSelf serviceSelf documenting
    26. 26. But, API publishers also want torestrict access to APIs
    27. 27. Smart rate limitingSecurity enforcementBrand control
    28. 28. Architects want API gateways API Gateway API
    29. 29. Developers demand API portals Portal
    30. 30. Tomorrow
    31. 31. websockets for bi-directional communication
    32. 32. Adaptive APIs –different strokes… API
    33. 33. The SSO saga will continue…
    34. 34. OpenID Connect will allowapps to retrieve end userInformation – with permission. User
    35. 35. Bring Your Own Device (BYOD) will drive a new generation of internal APIs BYOD
    36. 36. The battle for the definition of RESTwill continue...
    37. 37. Is this REST?
    38. 38. Or is this REST? HTTP Verbs URIs ?
    39. 39. Terminology is important…
    40. 40. ..but, focusing on design willimprove your API.
    41. 41. The hypermedia feature will become increasingly popular
    42. 42. Links will become a common facet ofWeb APIs
    43. 43. <bushel> <apple id=“23”/> </bushel>http://bushel/apple/23
    44. 44. <bushel> <link href=“http://bushel/apple/23”></bushel> http://bushel/apple/23
    45. 45. TheFuture
    46. 46. The hypermedia style will grow…
    47. 47. Templates for input Task based interaction Registered content types
    48. 48. Standards and conventionswill help us build generic APIs.
    49. 49. Smarter clients will call APIsthey didn’t even knowexisted.
    50. 50. ASmart APIClient B
    51. 51. …but new attack surfaces will lead to new exploits targeted at APIs
    52. 52. •Smarter Clients•Smarter attacks•Adaptive APIs•WebSockets and Open ID•Links in APIs•Mobile Consumers•Secure APIs•Internal and External APIs
    53. 53. Design long lasting APIswith your users in mind.
    54. 54. Trends in Web APIsRonnie MitraPrincipal API Architect - EMEALayer 7 API Academy