You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a mobile Nerves app that will experience periods of disconnection. Disconnected users will create/update/delete records, then re-sync upon connection.
I think this would be a good use-case for CRDTs. I'm curious if anyone has used CubDB with CRDTs, or if people can suggest other sync-strategies for disconnected updates.
The text was updated successfully, but these errors were encountered:
Not specifically for CRDTs, but for similar scenarios in embedded software where I needed to keep a queue for re-syncing when possible, I recently open-sourced CubQ, a durable queue and stack abstraction on top of CubDB. CubQ supports "at most once" and "at least once" semantics (for the latter, check the dequeue_ack/2 function).
I'm working on a mobile Nerves app that will experience periods of disconnection. Disconnected users will create/update/delete records, then re-sync upon connection.
I think this would be a good use-case for CRDTs. I'm curious if anyone has used CubDB with CRDTs, or if people can suggest other sync-strategies for disconnected updates.
The text was updated successfully, but these errors were encountered: