10-07-2020, 07:36 PM
One additional thought when syncing is to sync specific records. You do not have to sync the entire table.
- This makes the transaction more performant
- You improve security by only syncing data relevant to that user's data in the cdb_users table.
You can store their cdbRecordID to their cdb_users table in a local table, so you do not have to query for that data on every run of your app.
Working with the data locally, as Efrain said, is the most performant method possible. Should your app crash, or the client lose internet access, their data is store locally. The next sync will pick up the changes and send them to the cloud when conditions allow.
- This makes the transaction more performant
- You improve security by only syncing data relevant to that user's data in the cdb_users table.
You can store their cdbRecordID to their cdb_users table in a local table, so you do not have to query for that data on every run of your app.
Working with the data locally, as Efrain said, is the most performant method possible. Should your app crash, or the client lose internet access, their data is store locally. The next sync will pick up the changes and send them to the cloud when conditions allow.