Modeling RESTful Data Services


Right click “Save as…”

Slides (view online)
RESTful systems follow a specific set of design principles that enables scalability, layering, and proper separation of concerns for services exposed to the Web. In order to make it straightforward to create data services with a RESTful interface we introduced the ADO.NET Data Services Framework (Project code name "Astoria"). While the framework makes it easy to get a data service started, it still requires proper planning and design of the interface. In this session, we assume you're familiar with the basics of ADO.NET Data Services and we focus on how to approach the modeling of the application behavior in terms that match the architectural style proposed by REST, how to address common application needs such as authentication and authorization, and we discuss some guidelines for identifying when data services is a good tool for the job and when something else may be more appropriate.
For more information, check out this course on Microsoft Virtual Academy:

Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.