Named similarly as Doug Purdy's PDC 2010 session on oData, this OpenData for the Open Web session tries to explain how WCF Data Service with oData offers an accelerated path towards building a public API. The Web has been and should be open in almost all sense of the word: the web can be openly consumed from various clients, and through hyperlinking; the web allows the association of different documents across technological boundaries. The trend shouldn’t stop here. Web based API have and will continue to play a huge role in making sure that the web opens up even more. You will learn on how to take part of this movement in your own projects utilizing oData protocol. We will also talk about to why oData offer serious advantages than writing your own custom API specification to share your data. We will also talk about some of the opportunities that is opened up to us by using it. In this era of Cloud computing (the emergence of strong SaaS player like Facebook and Twitter), software is starting to become of a commodity and data becomes more and more precious – it’s important for us developers to understand the shift.

1. 8 – 10 March 2011 | Dubai, UAE

2. 8 – 10 March 2011 | Dubai, UAE Ronald Widha Open Data for the Open Web SESSION CODE: DEV

3. 3 Agendawhat I’m going to talk about The trend of Openness Select * from Web Common Web API patterns oData Marketplace Designing for high traffic

4. 4 Open Web decentralized transparency open standard new economy Photo by Creative commonsmiss_rogue

5. 5 Hypermedia

6. 6 Feeds Photo by Creative commonspresta

7. 7 API Photo by Creative commonssnowpeak

8. 8 Twitter Photo by Creative commonssnowpeak

9. 9 “API is the new biz dev”Caterina Fake Photo by Creative commonscaterina

10. 10 For e.g. Facebook API get friends Http GET: https://graph.facebook.com/me/friends?access_token=token JSON: { "data": [ { "name": “friends name", "id": "424248" }, .. ]} Photo by Creative commonskiewic

11. 11 For e.g. Twitter API get followers HTTP Gethttp://api.twitter.com/version/statuses/friends.xml?user_id=12& XML or JSON Photo by Creative commonskiewic

12. 12 Select * from Web Photo by Creative commons codepo8

13. 13 What about us (website owners/creators)? Photo by Creative commonsnasa HQ

14. 14 RESTful JSON Atom Xml feed oAuth for authentication/authorization Photo by Creative commonskiewic

15. 15 Why re-invent the wheel? Photo by Creative commonsdigitizedchaos

16. 16 Open Data (oData) RESTful Atom Xml feed JSON Photo by Creative commonskiewic

17. 17 Let me take you around Photo by Creative commonskiewic

18. 18 We’ve just seen Creating an Odata endpoint with WCF Data Services RESTful: Browsing Data using Browser Javascript as a client .Net client

19. 19 “Software is becoming a commodity”Tim O’ Reilly (Strata Conf) Photo by Creative commons adders

20. 20 Data Marketplace Photo by Creative commonskiewic

21. 21 Designing for the real world Performance Scalability Security Cache Photo by Bing Maps

22. 22 SQL Azure SQL Azure oData Service

23. Browser encrypt 23 Billing WCF Data Service Security https oAuth access Token or, Access control Authentication cookie Photo by Creative commonskiewic

24. 24 Service EndPoint Separate the reads and the writes writes replication reads Photo by Creative commonskiewic

25. 25 De-normalized for use cases Photo by Creative commonsbiepmiep

26. 26 Caching WCF Data Service Output caching vary by filter params Photo by Creative commonskiewic

27. 27 monitoring Photo by Creative commonskiewic

28. 28 WCF Data Services Toolkit JSONP Caching http://wcfdstoolkit.codeplex.com/ Photo by Creative commonskiewic

29. © 2008 Microsoft Corporation. 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.