4 ms·
I'm going to take an even harder line: Sync is a fundamentally broken. The only solution is to switch to technologies where merging data is a primary core fea
by zdw 14y ago
I'm going to take an even harder line:
Sync is a fundamentally broken.
The only solution is to switch to technologies where merging data is a primary core feature. Thus why I use text files and git to manage the vast majority of my data.
The sooner people realize that sync isn't fixable (or a good idea in many cases), the sooner real solutions appear.
- white_devil 14y agoSync is a fundamentally broken. Yep. It's weird that everything is built around just one button that says "Sync", when there are two different directions involved. Either you want to save the state of whatever device you're currently using, or you want to revert it to the state stored in the cloud. Export <--> Import, pretty much.
- mgkimsal 14y agowell, 'export but give me anything new that's not in conflict', or 'import but don't overwrite anything in conflict'... 'sync' somewhat makes sense, but two sync options labelled easy to understand would go a long way to clearing this up, but... would likely introduce other issues as well. 'sync' works fine, except for when it doesn't. :/
- jiggy2011 14y agoEven git isn't perfect. I spend plenty of time in a three windowed merge tool figuring out which piece of code should go where when we have merge conflicts. The solution would have to be to store everything in ascii formats (probably taking a hit in terms of filesize and performance) and get everyone to understand the ascii representation each of these data formats and how to merge them effectively. The alternative would be to build a diff tool for every binary based format out there. The simplest solution would simply be to implement locking on everything and have one authoritative copy. So you can have your data on any device you want and share it with as many others as you want but only one person/device can have write access at any given time and can only have that once they have updated to the latest version of that rescource.
- nradov 14y agoSynchronization in IBM Lotus Notes/Domino has worked quite well for 20+ years, so obviously sync is not fundamentally broken. More likely we've just failed to learn from history.
- elviejo 14y agoThat is why I like CouchDB. The original developer worked on the synchronization mechanism in Lotus Notes and used it in CouchDB.
- zdw 14y agoI'd love to know if the Notes sync method is documented somewhere. I don't doubt that there are some good implementations, but... Does it do offline sync with multiple users whose changes may have different priority? How about if time isn't set properly between multiple devices? How about a multi-way modify/delete/rename where two records are given identical keys on more than one system, then both systems are reconciled? I really need to write up a "Sync Gauntlet of Pain" that shows how sync implementations are incapable of making correct decisions, as they just don't have enough information, and giving them more information may not help.
- nradov 14y agohttp://www.ibm.com/developerworks/lotus/library/ls-Domino_Replication/ http://www.ibm.com/developerworks/lotus/library/ls-Domino_Re... http://www-12.lotus.com/ldd/doc/tools/c/8.5.2/api852ug.nsf/85255d56004d2bfd85255b1800631684/00d000c1005800c985255e0e00726863?OpenDocument http://www-12.lotus.com/ldd/doc/tools/c/8.5.2/api852ug.nsf/8... Yes it does offline sync with multiple users. Changes aren't prioritized but you can configure what it does with conflicts (merge if possible, discard, or leave the conflict). Time synchronization between multiple devices has been a solved problem for years. Not worth worrying about. Creation of identical record keys — while theoretically possible — really never occurs in practice.
- zdw 14y agoCool, thanks for the links! This looks like a really good system, and far more transparent in how it works vs. the "Black box" approach most systems use.
- pjscott 14y agoYou can do sync the Right Way, but it's non-trivial. Programs like Google Docs and Etherpad do really good sync for text documents, because they've put serious mental effort into figuring out how to get sync to work correctly under (almost) all possible circumstances. If ten people make conflicting edits to a single region of the document and then sync, their documents will provably reach a consistent and reasonable state. Many of the same methods can be applied to other types of synchronization, but it's more effort than most people can spare when they're in a hurry to get something released.
- eric-hu 14y ago> Sync is a fundamentally broken. It's for this reason I've been keeping my eye on Rich Hickey's Datomic. It's not open source or free, but the idea of immutable data (everything is attached to a timestamp--yes, everything), seems intriguing.