Trends in Web APIs Layer 7 API Management Workshop London
Download as PPTX, PDF6 likes1,905 views
The document discusses trends in web APIs, emphasizing the importance of user-centric design and the developer experience. It highlights the evolution of APIs from private to public usage, and the growing significance of security, flexibility, and standards like OAuth 2. Future trends include adaptive APIs, smart clients, and the integration of hypermedia features.
Trends in Web APIs Layer 7 API Management Workshop London
- 1. Trends in Web APIs Ronnie Mitra Principal API Architect - EMEA Layer 7 API Academy
- 2. The Layer 7 API Academy Mission: Ronnie Mitra Mike Amundsen To help API Publishers build great APIs Method: Conference Presentations Books, Blogs, Tutorials and Tech Talks Workshops and Mentoring
- 3. API
- 4. int printf ( const char * format, ... );
- 5. Web API
- 6. Web API = Technology
- 7. Is it a Web API? REST/JSON? Yes. SOAP/XML? Yes. HTTP/CSV? Yes.
- 8. Design APIs for your users. Developer experience is Paramount.
- 9. API
- 11. Today
- 12. Modern Timeline of Web APIs 2005 2004 2010 First Web 2.0 Programmable web.com Salesforce Conference adds HTTP API launched 2002 54 APIs Amazon API registered. 2005 2000 ebay makes 2008 2012 Salesforce API APIs free Programmable ebay API Programmable web.com has web.com has 2004 2006 1000 registered 7144 registered Flickr API Twitter API APIs APIs Facebook API Google (Maps) Sources: apievangelist.com programmableweb.com API internetarchive.com Steve Yegge Rant oreilly.com
- 14. The enterprise model: Start with private APIs…
- 15. …consider going public in the future
- 16. Mobile is driving API publishers
- 17. Bandwidth is a key constraint
- 20. HTTP-CRUD is the style of choice. GET PUT POST DELETE
- 21. Designers care about URI design /apple /apples /apples?colour=green /bushel/apples/
- 22. Security remains important API standards have emerged
- 23. OAuth 2 is gaining popularity
- 24. Flexibility is the new challenge SAML PKI LDAP WS-*
- 25. API publishers are becoming API consumers
- 26. The primary API management challenge: Balancing Control and Accessibility
- 27. API publishers want to encourage utilization
- 28. Low barriers to access Self service Self documenting
- 29. But, API publishers also want to restrict access to APIs
- 30. Smart rate limiting Security enforcement Brand control
- 31. Architects want API gateways API Gateway API
- 32. Developers demand API portals Portal
- 33. Tomorrow
- 35. websockets for bi-directional communication
- 36. Adaptive APIs – different strokes… API
- 37. The SSO saga will continue…
- 38. OpenID Connect will allow apps to retrieve end user Information – with permission. User
- 39. Bring Your Own Device (BYOD) will drive a new generation of internal APIs BYOD
- 40. The battle for the definition of REST will continue...
- 41. Is this REST?
- 42. Or is this REST? HTTP Verbs URIs ?
- 44. ..but, focusing on design will improve your API.
- 45. The hypermedia feature will become increasingly popular
- 46. Links will become a common facet of Web APIs
- 47. <bushel> <apple id=“23”/> </bushel> http://bushel/apple/23
- 48. <bushel> <link href=“http://bushel/apple/23”> </bushel> http://bushel/apple/23
- 49. The Future
- 50. The hypermedia style will grow…
- 51. Templates for input Task based interaction Registered content types
- 52. Standards and conventions will help us build generic APIs.
- 53. Smarter clients will call APIs they didn’t even know existed.
- 54. A Smart API Client B
- 55. …but new attack surfaces will lead to new exploits targeted at APIs
- 56. •Smarter Clients •Smarter attacks •Adaptive APIs •WebSockets and Open ID •Links in APIs •Mobile Consumers •Secure APIs •Internal and External APIs
- 57. Design long lasting APIs with your users in mind.
- 58. Trends in Web APIs Ronnie Mitra Principal API Architect - EMEA Layer 7 API Academy
Editor's Notes
- #11: Today = things we can see happeningTomorrow = things we know are out thereThe Future = things that we can speculate about, may or may not happen
- #13: Timeline EventsEvent: Salesforce.com API released (2000)Description: Salesforce.com 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 (developer.ebay.com) 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: Programmableweb.com 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)
- #14: API Growth is strong
- #17: Mobile is a key driver for APIs
- #57: Summary slide