Skip to main content

Developing an Application

 

Applies only to Mobile Apps
OutSystems

Offline Data Synchronization Patterns

In this section you can find a few common data synchronization patterns between your database and local storage entities. We provide these patterns as guidance in building the synchronization mechanism of your applications, so that you can adapt them to your needs and requirements.

For each synchronization pattern, we provide a working sample module that you can use to explore the implementation of the synchronization mechanism. Download an OutSystems application that contains all sample modules from the Forge.

We approach the following patterns:

  • Read-Only Data
    Use this synchronization pattern when your users only need to read data while the app is offline and the amount of data to synchronize is small.
  • Read-Only Data Optimized
    Use this synchronization pattern when your users only need to read data while the app is offline and there are large amounts of data to synchronize.
  • Read/Write Data Last Write Wins
    Use this synchronization pattern when it is not likely for more than one user to change the same data while the app is offline.
  • Read/Write Data With Conflict Detection
    Use this synchronization pattern when for advanced scenarios where more than one user will change the same data while the app is offline.
  • Read/Write Data One-to-Many
    This data synchronization pattern is recommended for mobile apps with entities that follow a one-to-many relationship and where it is not likely for multiple end-users to change the same data while the apps are offline.