Joomla in a world of ubiquitous computing
•Télécharger en tant que ODP, PDF•
0 j'aime•1,323 vues
Presentation slides given at the JoomlaDay UK 2013 event in Sunningdale, United Kingdon on 5 October 2013.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
En vedette
En vedette (7)
Similaire à Joomla in a world of ubiquitous computing
Similaire à Joomla in a world of ubiquitous computing (20)
Plus de Chris Davenport
Dernier
Dernier (20)
Joomla in a world of ubiquitous computing
- 1. Joomla in a world of ubiquitous computing Chris Davenport Joomla Production Leadership Team
- 2. Trends
- 3. More devices
- 7. More kinds of devices
- 13. More sensors
- 22. More kinds of sensors
- 27. More data
- 31. More kinds of data
- 35. More kinds of connectivity
- 42. The changing internet ● More devices ● More kinds of devices ● More sensors ● More kinds of sensors ● More data ● More kinds of data ● More connectivity ● More kinds of connectivity
- 43. And everything is getting Faster Smaller Cheaper
- 45. The marginal cost of adding new information capabilities to a product is offset by the added value either to the end-user or the supply chain.
- 47. Example The ability to gather more data about products throughout their lifecycles is changing the way many businesses operate.
- 48. Instead of “sell-it-and-forget-it” companies will maintain contact with their products throughout their lifecycles
- 50. Moving from selling products to selling services built around products
- 56. The Growth of APIs
- 58. Hide the details behind an interface that is Simple Consistent Stable over time
- 59. Allows you to treat a software package as a set of building blocks. So that blocks are interchangeable
- 66. Who uses web APIs? Google Twitter YouTube Flickr Amazon Facebook Twilio LastFM eBay Bing Del.icio.us Yahoo FourSquare Wikipedia
- 68. Hypermedia APIs Media + Links = Hypermedia
- 69. Surely big companies have had APIs for a long time...?
- 71. UNA:+.? ' UNB+IATB:1+6XPPC+LHPPC+940101:0950+1' UNH+1+PAORES:93:1:IA' MSG+1:45' IFT+3+XYZCOMPANY AVAILABILITY' ERC+A7V:1:AMD' IFT+3+NO MORE FLIGHTS' ODI' TVL+240493:1000::1220+FRA+JFK+DL+400+C' PDI++C:3+Y::3+F::1' APD+74C:0:::6++++++6X' TVL+240493:1740::2030+JFK+MIA+DL+081+C' PDI++C:4' APD+EM2:0:1630::6+++++++DA' UNT+13+1' UNZ+1+1'
- 72. Why hypermedia APIs? Scalability via load balancers and caches
- 73. Why hypermedia APIs? Loose coupling between sender and receiver Clients and servers can evolve independently of one another Driving application state by following links
- 74. Why hypermedia APIs? Open source Large community of developers Low cost of entry means that even very small businesses can use the technology
- 76. Silos are bad Unless you open them up, in which case... They become repositories Repositories are good
- 77. Add an API Lower the barriers to participation Use RESTful hypermedia standards Make it easy to share Publish the documentation Make it easy to sign-up for an API key Turning a silo into a repository
- 78. To a developer the API makes the organisation look like a resource that can be programmed like any other information system that has an API.
- 79. APIs change the relationships between organisations Traditional organisations are becoming “Programmable” organisations
- 80. Traditional business No or limited data sharing “Programmable” business Data sharing through open hypermedia APIs
- 81. Traditional business Constrained interaction with partners “Programmable” business Partners can interact in ways you hadn't thought of
- 82. Traditional business Limited partnering “Programmable” business Encourages an ecosystem of API users and developers who help grow the business
- 83. API Ecosystems Developers build applications that make use of the API Which attracts more users Which attracts more developers, and so on.
- 84. Expedia $2 billion per year through APIs “90% of what we do is business through APIs”
- 85. Internet of Things Hypermedia APIs
- 87. Disclaimer These are just my personal views. Please don't take them as being part of any official policy or direction of the Joomla project.
- 88. Joomla Framework should be the platform of choice for building Internet of Things applications Joomla CMS should be the platform of choice for building programmable organisations
- 89. How Joomla can help ● Make it easy to share data through hypermedia APIs – Subject to access control ● Make it easy to manage APIs – Developer/application registration – API key control – Rate-limiting, quotas, blocking ● Make it easy to remotely deploy and manage Joomla installations via the API ● Make it easy to add new content types via the API ● Make it easy to consume data from other APIs
- 90. Joomla now ● Primarily used to build websites ● Only supports mobile through responsive design ● No hypermedia API support ● Large, monolithic codebase ● Even components can't easily talk to one another
- 91. Joomla Next...?
- 92. ServicesSite UI Admin UI Web browser AJAX Hypermedia API HAL+JSON HAL+JSON HAL+JSON HTML HTML ServerClient
- 93. Web API (eg. AJAX) Get a list of articles: GET /joomla:articles GET /joomla:articles?page=3&perPage=10 Get a specific article: GET /joomla:articles/123 Update an article: PUT /joomla:articles/123 {”title”:”A new title for my content”, …}
- 94. Using the API directly (this is just a wild guess about what it might look like) Get a list of articles: $args = array('page' => 3, 'perPage' => 10); $input = new JInput($args); $controller = JController::getInstance('joomla:articles'); $response = $controller->get($input);
- 95. Services Hypermedia API HAL+JSON ServerClients Device 1 Device 2 Server HAL+JSON HAL+JSON
- 97. Services Hypermedia API HAL+JSON ServerClients PHP CLI PERL CLI Daemon HAL+JSON HAL+JSON
- 98. Services Site UI AJAX Hypermedia API HAL+JSON HAL+JSONHTML Ecommerce ServerWeb browser AJAX HAL+JSON Services Hypermedia API Transaction server (layout) (product data) (cart data - volatile) Angular JS
- 99. Joomla Next steps... ● Define a generalised hypermedia API – Web Services Working Group ● Define an architecture – With web services at the core ● Implement the standard in code ● Provide client-side SDKs ● API support for current core content types ● API support for UCM
- 100. A web API for Joomla? Github: https://github.com/chrisdavenport/j3-rest-api (Pull requests welcome, of course) Demo: http://demo.davenporttechnology.com/api Use the HAL browser from here: http://demo.davenporttechnology.com/api/hal- browser/browser.html#http://demo.davenporttechnology.com/api
- 101. Web Services Working Group http://docs.joomla.org/Web_Services_Working_Group