OData storage provider

OData is the leading solution for remote enterprise data access. It is a REST-based standard for querying and CRUD operations developed as the data access interface of Microsoft Azure storage, and adopted by a wide range of content providers and content management systems including SharePoint.

Where can I make use of OData

OData is an extremely powerful protocol, but the URI format makes its handling somewhat cumbersome, even with the plethora of tools and libraries developed to help handle it.

We see the OData provider as our central workhorse for heavy-duty data lifting in enterprise environments. You can interface your HTML5 intranet web application with your organizational datastores in SharePoint and SAP, or publish the data of your own .NET-based line-of-business application through a WCF Data Service, and make use of the JayData API to write your code in a straightforward and simple way, forgetting about the catches and intricacies of building OData requests.

If you are developing hybrid mobile applications commercially, the Azure Storage service can be an ideal data layer, quick to set up, safe and scalable at will, and you can use our OData provider to access the datastore in an easy manner.

The JayData added value

Our OData provider is a priority product, laden with features and going through continuous, rigorous testing. It supports the use of almost the full range of field operations in queries, and the allowed operations in projection statements are curtailed only by the limitations of OData itself.

You can focus on the data access logic itself, without burdening your code with URIs and HTTP methods. Also, the uniform API of JayData allows you to unburden your servers by offloading data to client-based WebSQL or SQLite datastores, lowering your hardware or cloud costs, without the need to work twice for the two datasources. Also note that the OData provider supports full read/write access.

We also include the Windows command-line tool jaysvcutil.exe, which allows you to autogenerate a JayData model definition from the metadata published by an OData service endpoint, streamlining development, and offering literally invaluable help in the case of huge enterprise data models with hundreds of tables and thousands of columns.

Provider peculiarities

The OData provider takes a single provider-specific argument, oDataServiceHost, which specifies the endpoint URL of the service.

Unfortunately, the limitations of the OData protocol do not allow field operations in projections via the map method, which becomes most painful when one wishes to display short previews from long text records, such as e-book excerpts or article lead-ins on a home page.

To overcome this limitation, such transformations should be defined on the serverside, and served as separate data fields.

, ,