Synchronizing data from disparate sources over two-tier, N-tier, and service-based architectures

We recently published a CTP of a technology used to sync various (even non-MS) online and offline datastores that I only just heard about and it's so cool I thought it worth sharing. Here is the link to the download; there is also some extensive documentation available now, which includes some code samples, there is a blog and another example app. It's very cool!




Microsoft Synchronization Services for ADO.NET provides the ability to synchronize data from disparate sources over two-tier, N-tier, and service-based architectures. Rather than simply 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 laptops and devices, that do not have a consistent or reliable network connection to a central server. It is crucial 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, which is modeled after the ADO.NET data access APIs, 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 count on a consistent network connection.