APIdays San Francisco, 06/22/2013

2,000 views

Published on

From Web APIs to Cross-Device Web Sites

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,000
On SlideShare
0
From Embeds
0
Number of Embeds
1,075
Actions
Shares
0
Downloads
32
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

APIdays San Francisco, 06/22/2013

  1. 1. FROM WEB APIS TO CROSS-DEVICE WEB SITESCreate & host web APIshttp://apispark.comJune 22, 2013Jérôme LOUVELjlouvel@restlet.comCEO
  2. 2. FROM CLASSIC WEB SITES TO WEB APIS2000 - 2010
  3. 3. CLASSIC WEB SITESITETool that allows a company to make key informationeasily accessible by end users,as hypermedia documents,WEB via the web protocols, offering the broadest accessibility.Web SiteHTML pagesBrowserHTTP/1.1
  4. 4. CLASSIC WEB SITES ARE PERFECTLY RESTFULREST purpose is the web of hypertextConstraints NotesClient-server client = user interface concerns (better UI portability)Stateless each client request must contain all the info necessary forthe server to respondCache allow client to reuse response data in a controlled mannerUniform interface efficient for large-grain hypermedia data transfersnot optimal for other forms of architectural interactionLayered system each component only knows about the immediatecomponent/layer it is interacting withCode on demand client component doesn’t know how to process theresources it has access to code representing this know-how is retrieved by the client and executed locally
  5. 5. EXPENSIVE STACKS REQUIREDJ2EE AppServerJava RuntimeWindowsHardwareNear 2000Proprietary stacks
  6. 6. THE IMPACT OF OPEN SOURCEMVC FrameworkApache TomcatJava RuntimeDebian LinuxHardwareNear 2005Licensing cost reductionCollaborative software innovation
  7. 7. EMERGENCE OF WEB APISE-Commercepionneers of APIsSocial webbillionaires of APIsCloud ComputingAPIs as a ProductMappingAPIs to see betterMobile AppsAPIs to stay connectedOpen DataAPIs to share data
  8. 8. WHAT IS A WEB API?A Tool that allows a company to make key informationP easily accessible by developers,I in a controlled way without exposing implementation details,WEB via the web protocols.Web APIDevice or program
  9. 9. WEB SITE + WEB APIREST FrameworkMVC FrameworkApache TomcatJava RuntimeDebian LinuxHardwareWeb APIs developed as a separate projectYou share the same database and container
  10. 10. REST FRAMEWORKS CAN HANDLE BOTHREST FrameworkApache TomcatJava RuntimeDebian LinuxHardwareUnifying and simplifying web developmentsNo need for MVC frameworks !
  11. 11. THE IMPACT OF CLOUD COMPUTINGREST FrameworkGeneric PaaSIaaSHardwareProprietary technology is back!But time and cost benefits are too strong…
  12. 12. Simpler, specialized, cost effectiveSimilarities with BaaS  no Backend to write!THE NEXT STEP: SPECIALIZED API PAASAPI PaaSIaaSHardware
  13. 13. ANATOMY OF A WEB APIIt’s less about the stack and more about the value providedStandard API contracts are key : AWS S3, Google Reader, Atom, etc.APIContractAPIImpl. #1APIImpl. #2APIprovider#1APIprovider#2
  14. 14. PROGRAMMABLE WEBComposition of public and private web APIs Time and cost reduction New value chainsComposite APIAPI nodeAPI node
  15. 15. WHAT REALLY MATTERS NOW?• The service or data that you are offering• Its cost of development, maintenance andoperations• Much less its open source nature– AWS, Twilio, Stripe and GitHub are proprietary!• As long as you have an Open API for it– and a freemium access Open APIs are the Open Sourcecomponents of the Cloud Computing era !
  16. 16. THE « WEB API » ARCHITECTURE STYLEThe limits of REST
  17. 17. WHAT REST IS NOT?• A buzzword for non-SOAP web APIs– BTW, most web APIs aren’t « REST APIs »– Most are not even RESTful / REST-minded but JSON-RPC API• Designed for non hypermedia-driven applications• Suited for machine-to-machine interactions– Require pre-existing knowledge, coupling between C/S• We need to stop the confusion !
  18. 18. A NEW ARCHITECTURE STYLE NEEDED• Keeping the best of REST– resource-orientation (URI, representations)– network interface (content negotiation, caching,conditional methods, etc.)• Replacing the rest of REST– no more HATEOAS blindly applied– mobile access is critical (off-line, small grained)
  19. 19. THE « WEB API » STYLEArchitecture style for Resource-Oriented Web APIsConstraints NotesClient-server client = machine (program or device)Stateless identical to RESTCache identical to RESTCustom interface predefined set of resources and representationsrequires coordination between clients and serversLayered system identical to RESTMobility intermittent and mobile Internet connectivity by design
  20. 20. REST AND WEB API STYLES ARE WEB BROTHERS
  21. 21. COMPARISON WITH WEB RPC
  22. 22. NEXT STEPS• API-Craft conference in Detroit, July 2013– http://restlet.github.io/web-api-style/– Contribute to the project
  23. 23. FROM WEB APIS TO CROSS-DEVICE WEB SITES
  24. 24. WEB APIS ARE NOT THE MOST IMPORTANT• They only give access to something else– valuable data, service, device• End-users/consumers don’t care about them• Business persons don’t really understandthem and will likely never do so• What does really matter then?
  25. 25. A NEW GENERATION OF WEB SITES !Web SitePages + APIBrowserConnectedmobile devicesSmartenvironnementPartner Internal ISCROSSDEVICESITETool that allows a company to make strategic informationeasily accessible by any kind of machine, on behalf of humans,using best UI paradigm in the given context for a consistent UX,WEB via the web protocols.
  26. 26. FINAL THOUGHTS• The « API economy » is an intermediary step• APIs enable the Cross-device User eXperience• Everyone will care for it!Source: Wired / June 2013
  27. 27. KEEP IN TOUCH!Printed book launchedlast September !http://apispark.comTwitter: @jlouveljlouvel@restlet.com

×