Orcas CTP: Synchronization Services

Just looking over the latest Orcas CTP I noticed something new:

Synchronization Services lets you synchronize data from disparate sources over two-tier, N-tier, and service-based architectures. Instead of only replicating a database and its schema, the Synchronization Services application programming interface (API) provides a set of components to synchronize data between data services and a local store. Applications are increasingly used on mobile clients, such as portable computers and devices, that do not have a consistent or reliable network connection to a central server. It is important for these applications to work against a local copy of data on the client. Equally important is the need to synchronize the local copy of the data with a central server when a network connection is available. The Synchronization Services API is modeled after the ADO.NET data access APIs and gives you an intuitive way to synchronize data. It makes building applications for occasionally connected environments a logical extension of building applications where you can depend on a consistent network connection.

This looks like a great addition to ADO.NET for the .NET 3.5 release. Be sure to check out Rafik’s blog on synchronization services…