Overview of sync methods?
Is there any documentation that outlines the fundamental architecture behind the various sync options? While I’ve found setup guides for each method, I’m particularly interested in understanding how each one works under the hood. My goal is to select a sync method that best fits my needs while also being as straightforward and reliable as possible from your perspective. Of all the supported sync methods, which are considered the most robust and low-maintenance?
Not really, although the code is public.
At a high level, the most reliable clients are the dropbox and the git client. The dropbox and google drive clients work in similar ways: the relevant service's API notifies Blot via a webhook when there are folder changes, and Blot fetches those changes. In practice, Dropbox is much faster to notify us of changes and it offers more robust and reliable ways to compute the delta between the state of your folder. Google Drive's change notifications are often minutes late, and although their API documentation claims to offer ways to query folder state changes efficiently, in practice they do not.
The git client is robust in the sense that it requires no third-party. Communication is between the git program on your device, and the git server running on Blot. However, our setup is a little less sturdy when you're pushing large files (>10mb). There are steps to improve this, which I will take.
The icloud client is the newest sync method and by far the least reliable. As it is used by more people, I'll uncover more bugs and improve the reliability. Generally, the older the client, the more stable it is because it's been used and tested by more of our customers.
Please let me know if you have any questions about this or anything else
Answered a month ago · Edit answer