![10For e.g. Facebook API get friendsHttp GET: https://graph.facebook.com/me/friends?access_token=tokenJSON: { "data": [ { "name": “friends name", "id": "424248" }, .. ]}Photo by Creative commonskiewic](https://image.slidesharecdn.com/opendataforopenweb-110307042416-phpapp02/85/DPR202-Open-Data-for-the-Open-Web-10-320.jpg)
![10For e.g. Facebook API get friendsHttp GET: https://graph.facebook.com/me/friends?access_token=tokenJSON: { "data": [ { "name": “friends name", "id": "424248" }, .. ]}Photo by Creative commonskiewic](https://image.slidesharecdn.com/opendataforopenweb-110307042416-phpapp02/75/DPR202-Open-Data-for-the-Open-Web-10-2048.jpg)
Uploaded byRonald Widha
DPR202 Open Data for the Open Web
The document discusses the trend of openness in web development, focusing on open data, APIs, and their role in creating efficient, scalable services. It highlights practical examples, such as Facebook and Twitter APIs, and mentions the importance of performance, security, and caching in designing for high traffic. Additionally, it emphasizes the shift towards RESTful services and open standards in the new economy.
More Related Content
Similar to DPR202 Open Data for the Open Web
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
DPR202 Open Data for the Open Web
- 1. 8 – 10March 2011 | Dubai, UAE
- 2. 8 – 10March 2011 | Dubai, UAERonald WidhaOpen Data for the Open WebSESSION CODE: DEV
- 3. 3Agendawhat I’m goingto talk aboutThe trend of OpennessSelect * from WebCommon Web API patternsoDataMarketplaceDesigning for high traffic
- 4. 4Open Webdecentralizedtransparencyopen standardneweconomyPhoto by Creative commonsmiss_rogue
- 5.
- 6. 6FeedsPhoto by Creativecommonspresta
- 7. 7APIPhoto by Creativecommonssnowpeak
- 8. 8TwitterPhoto by Creativecommonssnowpeak
- 9. 9“API is thenew biz dev”Caterina FakePhoto by Creative commonscaterina
- 10. 10For e.g. FacebookAPI get friendsHttp GET: https://graph.facebook.com/me/friends?access_token=tokenJSON: { "data": [ { "name": “friends name", "id": "424248" }, .. ]}Photo by Creative commonskiewic
- 11. 11For e.g. TwitterAPI get followersHTTP Gethttp://api.twitter.com/version/statuses/friends.xml?user_id=12&XML or JSONPhoto by Creative commonskiewic
- 12. 12Select * fromWebPhoto by Creative commons codepo8
- 13. 13What about us(website owners/creators)? Photo by Creative commonsnasa HQ
- 14. 14RESTfulJSONAtom Xml feedoAuthfor authentication/authorization Photo by Creative commonskiewic
- 15. 15Why re-invent thewheel?Photo by Creative commonsdigitizedchaos
- 16. 16Open Data (oData)RESTfulAtom Xml feedJSONPhoto by Creative commonskiewic
- 17. 17Let me takeyou aroundPhoto by Creative commonskiewic
- 18. 18We’ve just seenCreatingan Odata endpoint with WCF Data ServicesRESTful: Browsing Data using BrowserJavascript as a client.Net client
- 19. 19“Software is becominga commodity”Tim O’ Reilly (Strata Conf)Photo by Creative commons adders
- 20. 20Data MarketplacePhoto byCreative commonskiewic
- 21. 21Designing for thereal worldPerformanceScalabilitySecurityCachePhoto by Bing Maps
- 22. 22SQL AzureSQL AzureoData Service
- 23. Browserencrypt23BillingWCF Data ServiceSecurityhttpsoAuthaccess Token or,Access controlAuthentication cookiePhoto by Creative commonskiewic
- 24. 24ServiceEndPointSeparate the readsand the writeswritesreplicationreadsPhoto by Creative commonskiewic
- 25. 25De-normalized for usecasesPhoto by Creative commonsbiepmiep
- 26. 26CachingWCF Data ServiceOutputcaching vary by filter paramsPhoto by Creative commonskiewic
- 27. 27monitoringPhoto by Creativecommonskiewic
- 28. 28WCF Data ServicesToolkitJSONPCachinghttp://wcfdstoolkit.codeplex.com/Photo by Creative commonskiewic
- 29. © 2008 MicrosoftCorporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.