Fluree and asychronous / disconnected operations #131
-
|
Can Fluree handle asychronous / disconnected operations where we would possibly sync multiple instances at different times......let’s say we have 200 instances of the DB all with different users and they sync their individual device asynchronously so that each device syncs to a master instance all at different times. Would this work with Fluree? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Sure, assuming the transactions won’t be of a type that might conflict with one another. i.e. if every user is just updating their own data. Would they all be running a local DB? You can also do forward time travel - where you propose transactions but don’t commit them. That would keep a local DB with an optimistic view of txns and then you actually transact once connected. There isn’t a way this happens today fully automatically so there would be some work on the app side - but all the hooks are there. |
Beta Was this translation helpful? Give feedback.
Sure, assuming the transactions won’t be of a type that might conflict with one another. i.e. if every user is just updating their own data. Would they all be running a local DB? You can also do forward time travel - where you propose transactions but don’t commit them. That would keep a local DB with an optimistic view of txns and then you actually transact once connected. There isn’t a way this happens today fully automatically so there would be some work on the app side - but all the hooks are there.