GAINING THE KNOWLEDGE OF THE OPEN DATA PROTOCOL

(ODATA)Chris Woodruff

WHO I AM?

Chris Woodruff

MVP, Visual C#

Director at Perficient

Co-host of Deep Fried Bytes Podcast

@cwoodruff / cwoodruff@live.com

Skype: cwoodruff

YOU WILL LEARN:

Understand the background of OData

Have an understanding of the OData protocol

How to produce an OData feed using WCF Data Services

How to produce an OData feed using ASP.NET Web API

How to consume an OData feed using LINQ

BACKGROUND

Knowledge of OData

QUOTE

Today, the tools for capturing data both at the mega-scale and at the milli-scale are just dreadful. After you have captured the data, you need to curate it before you can start doing any kind of data analysis, and we lack good tools for both data curationand data analysis.

Jim Gray

Problem: Data APIs frequently create more problems than

solutionsTHIS TALK IS ABOUT ONE SOLUTION.

SURVEY

…knows what the web is

…are comfortable w/ HTTP and XML? JSON?

…have a basic understanding of the term REST

…have created a Data API

Is there really a problem?What is it?

QUIZ TIME

FACEBOOK: WHAT FIELDS WILL I GET WHEN I READ A POST?

FACEBOOK: HOW DO YOU LIKE A POST?

How do developers know what to do?

SO GIVEN THAT NOBODY KNEW THE ANSWERS TO THESE QUESTIONS,

I GUESS THEY USE DOCS

So is there really a problem?Yes

DEVELOPERS DON’T HAVE TIME TO ACTUALLY READ THE DOCS

Can OData Magically cure the problem? No, but it can help.

LET’S SEE HOW

THE PROTOCOL

Knowledge of OData

THE BASICS OF ODATA

Feeds, which are Collections of typed Entities

OData services can expose Actions and Functions (v4), Services (v3)

OData services expose all these constructs via URIs

OData service may also expose a Service Metadata Document

FULL SQL LIKE QUERY “LANGUAGE”

HTTP Command (Verb)

SQLCommand

GET SELECT

PUT UPDATE

POST INSERT

DELETE DELETE

THE $METADATA ENDPOINT

CONVENTIONS

http://services.odata.org/OData/OData.svc

\_______________________________________/

|

service root URI

http://services.odata.org/OData/OData.svc/Category(1)/Products?$top=2&$orderby=name

\_______________________________________/ \__________________/ \_________________/

| | |

service root URI resource path query options

URL CONVENTIONS

$filter

/Suppliers?$filter=Address/City eq 'Redmond‘

$orderby

/Products?$orderby=ReleaseDate asc, Rating desc

$top and $skip

/Products?$top=5&$skip=2

$select and $expand

/Products?$select=*,Category/Name&$expand=Category

COMBINING UEL CONVENTIONS

http://.../Players/ ?$skip=10

&$top=2

&filter=substringof(‘Wood',nameLast)

&$orderby=nameLast%20desc

&$select=nickname,yearBorn,nameFirst

&$format=json

PAYLOAD CONVENTIONS

Success and error Codes 200 OK, 201 Created, 415 Unsupported Media Type, etc

Overall Format JSON

AtomPub

JSON Verbose

Nuances PATCH, Null payloads, etc

JSON FORMAT

Friendly to Javascript

90% more compact than AtomPub

Reads like a custom API

Very little OData “gunk”

ATOM FORMAT

Atom parsers exist in many frameworks

Element fields can be mapped to their Atom counterparts

A good example of OData interoperability

WHAT ELSE CAN YOU DO WITH ODATA?

Actions and Functions allow hypermedia-based method calls (non-CRUD operations)

Defined conventions for PATCH and deep insert

Vocabularies

ODATA ISN’T ALWAYS THE BEST FIT

OData may not be a good fit for highly opinionated APIs laden with developer intent

OData may not be a good fit for bulk data transfer

OData may not be a good fit for the APIs that dramatically different in shape than the backend

ODATA DOES NOT SUPPORT ALL QUERIES

OData doesn’t currently support aggregation You can’t ask for customers that have at least 2 orders

OData doesn’t currently support filters expansions You can’t ask for a customer and only their orders placed in 2013

OData doesn't support “graph” queries You can ask friend-of-a-friend type queries, but there are limitations

ODATA IS A STANDARD!!

OASIS, ISO

Ratified in March!

WHO USES ODATA?

WHAT DOES ODATA GIVE ME AND MY ORGANIZATION?

Empower Internal Power Users

Empower Existing and Future Customers

Monetize Data for untapped Revenue

CREATING FEED W/ ASP.NET WEB API

Knowledge of OData

ASP.NET WEB API

DEMO

ODATA BEST PRACTICES (PRODUCER)

Always design your OData feed will server-side paging if your entity collections hold large amounts of data.

Looks at server-side validation of queries and data updates based on the user credentials sent through HTTP

CONSUMING ODATA

Knowledge of OData

WHAT IF DATA API’S WERE LIKE…

LINQ? What are the last 50 invoices we sent?

context.Invoice.OrderByDescending(i=>i.PostedAt).Take(50);

What are the invoices from the last 24 hours? context.Invoice.Where(i=>i.PostedAt > DateTime.Now.AddDays(-1));

How many $1M invoices have we sent? context.Invoice.Where(i=>i.TotalAmount >= 1000000);

ODATA BEST PRACTICES (CONSUMER)

Use Query Projection to only bring back the entity properties you or your app needs.

Think about client-side paging even if their exists server-side paging.

Design and implement a client-side data caching function in your app (unless sensitive data).

WHY ARE WE EXCITED!!

WRAP-UP

Knowledge of OData

The demo projects can be found at:

github.com/cwoodruff/

RESOURCES

REST

http://www.ics.uci.edu/~taylor/documents/2002-REST-TOIT.pdf

OData

http://odata.org

http://odataprimer.com

CONTACT ME

Chris “Woody” Woodruff

cwoodruff@live.com

Twitter @cwoodruff

Skype cwoodruff

http://chriswoodruff.com

http://deepfriedbytes.com