Developing RESTful Services in .NET

For more information see www.bbd.co.za and www.drp.co.za

Look at creating RESTful Services using .NET

NOT covering

Design Patterns

Best Practises*

Acronym?

Representational State Transfer

Source?

Came about in 2000 doctoral dissertation of Roy Fielding

ROA – Resource Orientated ArchitectureWOA – Web Orientated Architecture Thanks Gartner for another TLA It is a styleNOT API Interface Official Standard A drop in replacement for SOAP

ASP.NET WebForms

ASP.NET MVC

WCF Data Services

WCF REST

3rd Parties

Demo in all 4 .NET technologies

Full CRUD on Games

Focus on the REST – Ignore the rest (i.e black box)

Work in JSON

A RESTful Service

WebForms

Not really built for this

Need to EVERYTHING

Not recommended unless you have no other option

MVC

A lot better than WebForms

Helper methods for handling method type, jsonetc…

Multiple return types means more work

WCF Data Services

All done for you

Good security model

Designed with data solutions in mind

Issues if not using EF (non-POCO)

Powerful client side options

OData Format

WCF REST

Loads of helpers

Designed with REST in mind

Not tied to data solutions

Powerful clients

WebForms + MVC

WCF REST + WCF Data Services

MVC + WCF Data Services