InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

ADO.NET Data Services Is About to Go Offline

Posted by Abel Avram on Nov 04, 2008

Sections
Architecture & Design,
Development,
Operations & Infrastructure
Topics
.NET ,
Data Access
Tags
Astoria ,
ADO.NET

 ADO.NET Data Services, previously known as Project Astoria, will receive offline capabilities in the near future. That means applications could be developed to synchronize their data, then use it in an offline fashion.

Project Astoria, which later became ADO.NET Data Services and was included in Visual Studio 2008 SP1, allows developers to access databases through a service proxy, simplifying database access and data retrieval/storage. Saaid Kahn, Program Manager on the Visual Studio Pro Tools team, explains in an interview how to create an n-tier application accessing a database using ADO.NET Data Services.

Astoria uses RESTful services and offers an URI as service access point. Currently, data can be accessed only online, but there are plans to release an alpha version which will allow offline data access soon, and will make use of the Microsoft Sync Framework. The purpose of the alpha release is to collect feedback to see if the direction followed is the right one and is planned to happen this year, according to Pablo Castro, a software architect at Microsoft.

Pablo has outlined some of the scenarios they are considering in going offline with ADO.NET Data Services:

  • Synchronization with intranet databases
  • Synchronization with cloud based data
  • Data consolidation. Data could be provide by several services retrieving it from various sources: databases, cloud, custom repositories.

Pablo has revealed the guidelines followed by their team:

We will stick to a simple and open interface. ... Anybody with an HTTP client and enough knowledge of our sync strategy should be able to synchronize with a data service.

Data independence will remain there for sync as it is already for online access. ... If the data service is sync-enabled you can sync with it, no matter what backs it.

We are targeting data services for structured stores and business applications. That implies a certain level of sophistication in the shape of data, such as assuming cross-item dependencies, store-level and application-level constraints that dictate consistent states of data, the need for making partial progress during synchronization, etc.

In a recent video interview, Pablo and Waseem Basheer, an Astoria developer, make a preview of the alpha release. Astoria Offline, as they call it, has been also presented during PDC 2008.

No comments

Watch Thread Reply

Educational Content

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.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.