Sync Data Between Devices - .NET SDK
Overview
Atlas Device Sync automatically synchronizes data between client applications and an Atlas App Services backend. When a client device is online, Sync asynchronously synchronizes data in a background thread between the device and your backend App.
When you use Sync in your client application, your implementation must match the Sync Mode you select in your backend App configuration. The Sync Mode options are:
Partition-Based Sync
Flexible Sync
You can only use one Sync Mode for your application. You cannot mix Partition-Based Sync and Flexible Sync within the same App.
Tip
See also:
Partition-Based Sync
When you select Partition-Based Sync for your backend App configuration, your client implementation must include a partition value. This is the value of the partition key field you select when you configure Partition-Based Sync.
The partition value determines which data the client application can access.
You pass in the partition value when you open a synced realm.
Flexible Sync
When you select Flexible Sync for your backend App configuration, your client implementation must include subscriptions to queries on queryable fields. Flexible Sync works by synchronizing data that matches query subscriptions you maintain in the client application.
A subscription set contains a set of queries. Realm Flexible Sync returns documents matching those queries, where the user has the appropriate permissions to read and/or read and write the documents. If documents match the query, but the client does not have the permission to read or write them, they do not sync to the client application.
You can form queries using Realm Query Language or LINQ.
Note
Flexible Sync does not support all the query operators available in Realm Query Language and the SDK's query engine. See Flexible Sync RQL Limitations for details.
Subscription sets are based on a specific type of Realm object. You can have multiple subscriptions if you have many types of Realm objects.
To use Flexible Sync in your client application, open a synced realm with a Flexible Sync configuration. Then, manage subscriptions to determine which documents to sync.
Group Updates for Improved Performance
Every write transaction for a subscription set has a performance cost. If you need to make multiple updates to a Realm object during a session, consider keeping edited objects in memory until all changes are complete. This improves sync performance by only writing the complete and updated object to your realm instead of every change.
Unidirectional Sync
A special case of Flexible Sync is when you need your app to send data to Atlas, but not receive any updates.
In this scenario, you can maximize sync performance by using Asymmetric Sync to stream data from the client application to a Flexible Sync-enabled Atlas App Services App.