How to update local parse.com database incrementally?

Question

i have a parse.com based app with offline capabilities where the whole database is stored locally (localStorage on web clients and parse.com local database on mobile clients). I am looking for a design solution to efficiently update the local database with latest changes in the remote database. The options that I could think of are:

Journaling with code triggers. Setup cloud code triggers (afterSave, afterDelete) for every object and add a log to the journal table every time an object has been saved or destroyed. The clients will query the table for updates and remember lastUpdateTime for subsequent requests.

Pros: a) we can have a very detailed summary what has been changed and who made the change. b) all the changes are instantly available for other clients (e.g. table call be polled for notifications in real time with little delays)

Cons: a) there may be too many entries in the table
Journaling with background job. Setup a background job that queries all tables by updatedAt, populates journal table and saves the lastUpdateTime for subsequent requests.

Pros: a) less entries in the journal table

Cons: a) changes are available with unpredictable delay (not suitable for real time notifications?) b) cannot track deletes, there's still a need to setup another table to track deletes or implement soft-delete c) less details in the log (e.g. when object is created by one user and deleted by another user, we will not know who created an object)
No journal. All clients query all tables by updatedAt and store lastUpdateTime for subsequent requests.

Pros: a) easy to implement, b) changes are instantly available

Cons: a) same problem with deletes as in 2, b) inefficient (i believe that querying 20+ tables by all clients is not a good idea

We also have an UI where user can look through the recent activity (who changed what), so I kind of lean towards number 1 approach, but the potential size of the table is worrying me.

Are you using parse pin? parse.com/tutorials/using-the-local-datastore — Faizan Tariq
– Faizan Tariq, Commented Aug 31, 2015 at 12:05
Are you limited to any libraries or are you open to using native javascript? — THE AMAZING
– THE AMAZING, Commented Sep 3, 2015 at 21:28

lazy · Accepted Answer · 2015-09-01 05:04:29Z

1

Client needs ability to recover irrespective of current state. This is critical if you are using local storage that may get cleared by the user. In that case you need a recoverable state. Additionally the client needs to be able to fetch only the transaction required / relevant to it.

Implementing a transaction store on the backend
Creating a recovery mechanism in case the localstorage offline is corrupted
Journaling with code triggers or use of event source db type mechanism so that you have complete history and can use that to build tables for the client.

In conclusion - Modified Journaling with Code Triggers (Modified to recover and storing the state for client in server and using that to query the data)

answered Sep 1, 2015 at 5:04

lazy

5312 silver badges4 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How to update local parse.com database incrementally?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related