New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Astoria: Microsoft's RESTful Data Services
Posted by Hartmut Wilms on May 04, 2007
Microsoft's RESTful Data Services
Microsoft announced the Project Astoria MIX '07. Astoria offers a RESTful approach to expose data as data services on the web.
The Astoria Online Service describes the goal of Microsoft Astoria as
[...]to enable applications to expose data as a data service that can be consumed by web clients within a corporate network and across the internet. The data service is reachable over HTTP, and URIs are used to identify the various pieces of information available through the service. Interactions with the data service happens in terms of HTTP verbs such as GET, POST, PUT and DELETE, and the data exchanged in those interactions is represented in simple formats such as XML and JSON.
The Microsoft Codename "Astoria" Overview document shows how data is addressed and represented by Astoria data services. In order to address data with Astoria data services the following addressing scheme is used: http://host/vdir/
Predicates can be integrated into resource URIs, e.g. http://myserver/data.svc/Customers[City eq 'London'], as well as query string options, which control the output:
http://myserver/data.svc/Customers?$orderby=City
http://myserver/data.svc/Customers?$top=5
http://myserver/data.svc/Customers?$skip=30&$take=10
Concerning the output or data representation Astoria supports plain XML, JSON (JavaScript Object Notation) and a subset of RDF+XML. The default data representation is XML, e.g. http://myserver/data.svc/Customers[ALFKI] might respond with:
<DataService xml:base="http://myserver/data.svc"> <Customers> <Customer uri="Customers[ALFKI]"> <CustomerID>ALFKICustomerID> <CompanyName>Alfreds FutterkisteCompanyName> <ContactName>Maria AndersContactName> <ContactTitle>Sales RepresentativeContactTitle> <Address>Obere Str. 57Address> <City>BerlinCity> <Region /> <PostalCode>12209PostalCode> <Country>GermanyCountry> <Phone>030-0074321Phone> <Fax>030-0076545Fax> <Orders href="Customers[ALFKI]/Orders" /> Customer> Customers> DataService>
The root "DataService" always contains the base URI of any resource represented by the service. Navigational nodes, which represent associated resources, contain relative URIs. In the example the orders of customer "ALFKI" are pointed to by the concatenation of the base URI (within the root node) with the relative URI (within the Orders node): "http://myserver/data.svc" + "/" + "Customers[ALFKI]/Orders".
According to Microsoft Astoria offers an easy way of implementing RESTful web services primarily targeted at providing data. In addition to GETting data from a data service data can also be updated or inserted via HTTP PUT or HTTP POST.
Udi Dahan is very skeptical about the usefulness and relevance of Astoria and Microsoft's data service approach in general:
But I’ve got to say, I’ve been against these “data services” from day one. The REST style is most applicable for large, chunky resources - while this seems to be targeting single tables in the database. Look at this discussion on REST vs SOA for some examples.
Danny Ayers, on the other hand, thinks that Microsoft approaches the Semantic Web with Astoria. Alex James provides an expansive overview of the Astoria buzz.
No comments
Watch Thread Reply