2. 2 ADO.NET Data Services for the Web Mike Flasko Program Manager, Microsoft “Project Astoria”

3. 3 Agenda Why ADO.NET Data Services? Characteristics of a data service Creating and consuming services Product Roadmap Summary: A data platform for the web

4. 4 Why ADO.NET Data Services? HTML + Javascript Data (XML, etc) DLL + XAML Data (XML, etc) Mashup UI Data Feeds AJAX Applications Silverlight Applications Online Services Mashups

5. 5 A REST Interface for Data The underlying model Entities and associations  resources and links Entity Data Model Every resource is addressable via a URI Flexible URI scheme for data retrieval URIs Data as resources, HTTP verbs to manipulate it Leverage caching, proxies, authentication, … HTTP AtomPub, JSON Formats

6. 6 Data Source Provider Creating Data Services Create services directly from Visual Studio Various data sources – Entity Framework – LINQ providers Model-driven – Structural description in Entity Data Model – Schema shapes the service contract Entity Framework Custom LINQ provider Relational database Other sources Data Services Runtime Hosting/HTTP Listener HTTPHTTP IQueryable [+ IUpdatable]

7. 7 Securing and Extending Services Per-container visibility control Read, Query and Write options Visibility Integrate with hosting environment ASP.NET, WCF or custom authentication schemes Authentication Execute before HTTP GET/PUT/POST/DELETE Enable validation, custom row-level security policies Maintain the REST interface Interceptors Custom entry points, e.g. /MyTags?startDate='2007-01-01' Composable, follow URI scheme Service Operations

8. 8 Refining Data Services Optimistic Concurrency Integrates with EF notion of concurrency tokens per type Uses existing HTTP semantics (ETags) Batching Create responsive, operation intensive applications Enables “all or nothing” groups of CUD operations Versioning Simple versioning scheme Allows clients & servers to version at different speeds Error Handling & Contracts Map exceptions in service-tier to platform independent, HTTP-friendly responses Debug mode to control verbosity of error information on the wire

9. 9 Talking to Data Services An HTTP stack is enough AtomPub clients.NET Framework & Silverlight 2 – LINQ to ADO.NET Data Services Framework AJAX (CodePlex) In future: ASP.NET Data Source Control

10. 10 AtomPub in Windows Live & Data Services AtomPub Unified Development Story Visual Studio.NET and Silverlight 2 ASP.NET Integration AJAX library 3 rd party components Consumer Services e.g.: Windows Live Spaces (Photos) e.g.: Windows Live Spaces (Photos) Infrastructure Services e.g.: Application- Based Storage SQL Server Data Services e.g.: Application- Based Storage SQL Server Data Services On-Premises Services e.g.: Data Services framework using local SQL Server e.g.: Data Services framework using local SQL Server

11. 11 Roadmap & Summary Shipped CTPs in 2007 as “Project Astoria” – A proof of concept to gather feedback Released to production as part of.NET Fx 3.5 SP1 – Started from scratch and built a production-quality version Silverlight 2 client to RTW with Silverlight 2 SDK Working on V2 data services V2 – Containment – "Astoria Offline" – We want to hear from you...

12. 12 Resources Team Blog: http://blogs.msdn.com/astoriateamhttp://blogs.msdn.com/astoriateam Online Forum: – Search "ADO.NET Data Services": http://forums.microsoft.comhttp://forums.microsoft.com Data Developer Center: – http://msdn.microsoft.com/datahttp://msdn.microsoft.com/data Email me: mike.flasko@microsoft.commike.flasko@microsoft.com

13. 13

14. 14 Resources www.microsoft.com/teched Tech·TalksTech·Ed Bloggers Live SimulcastsVirtual Labs http://microsoft.com/expression Professional Design tools for tomorrow http://msdn.microsoft.com Developer’s Kit, Licenses, and MORE!

15. 15 © 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.