What was Syncthing picked over the many alternatives?
Context
Please see: Files vs web pages. In the context of WikiSuite, we already have two other software components that manage files
- ClearOS Flexshare, which provides a standard file server, with three interfaces: 1- Web (HTTP/HTTPS) 2- FTP (FTP/FTPS) 3- File Shares (Samba)
- However it has the weaknesses of standard files and folders: no meta data, file needs to be in only one folder, or it's duplicated, hard to segment permissions, etc.
- Tiki File Galleries, which provide virtual folders and sub-folders which are web accessible. This abstraction layer permits multiple features: archives (previous versions of a file can still be accessed), check-in / check-out / lock, etc. and it leverages Tiki's multitude of built-in features: search (including file content), share secret link to file via email, permissions, etc. It's even possible to use as a field type in Tiki Trackers, a powerful and flexible database, form and report creator.
- However, it has the weakness that the only reliable interface is the web interface
By using each tool when it's appropriate, we have a good solution for most use cases. However, file sync was missing. An extensive analysis of all available Free / Libre / Open Source software was conducted, and Syncthing was deemed the best component to complete the feature set.
Beyond satisfying the usual component criteria, Syncthing's P2P design is awesome.
- P2P by default, so same software (it's cross platform) on all nodes. Central server is just a convention.
- This is much less work than having different code bases to manage
- It is designed from the ground up to sync any number of nodes. So a node can get data updates from any other node.
- Syncthing is written in Go, which has fantastic performance (which is important when you have a lot of files)
- Default interface is a Bootstrap admin panel, and clients can make alternate interfaces such as Syncthing-GTK for better integration with operating system.
- https://github.com/syncthing/syncthing/blob/master/GOALS.md
- While Syncthing is P2P (and thus, shared folders contain everything), there is a way to browse Syncthing folders and cherry-pick files to download. This makes it more like a client-server.
Why not ownCloud / Nextcloud
- This would have been easier since there was already an app for ClearOS but:
- Way too much overlap between Tiki Wiki CMS Groupware and ownCloud / Nextcloud. It's way less work to add / improve any missing functionality in Tiki than to deal with overlap.
- The server and clients are different code bases, which is bigger long term workload.
- Can't do P2P sync. Everything needs to go via central server.
Why not Seafile
- Seafile is an interesting project but
- Way too much overlap between Tiki Wiki CMS Groupware and Seafile. It's way less work to add / improve any missing functionality in Tiki than to deal with overlap.
- The server and clients are different code bases, which is bigger long term workload.
- Can't do P2P sync. Everything needs to go via central server.
Why not Pydio
- Pydio is an interesting project but
- Way too much overlap between Tiki Wiki CMS Groupware and Pydio. It's way less work to add / improve any missing functionality in Tiki than to deal with overlap.
- The server and clients are different code bases, which is bigger long term workload.
- Can't do P2P sync. Everything needs to go via central server.
Why not SparkleShare
- SparkleShare is an interesting project but
- Way too much overlap between Tiki Wiki CMS Groupware and SparkleShare. It's way less work to add / improve any missing functionality in Tiki than to deal with overlap.
- It's based on Git whereas Syncthing uses the Block Exchange Protocol which is more suited for this use case
- Can't do P2P sync. Everything needs to go via central server.
Why not LinShare
- LinShare is an interesting project but it is for file sharing and not file sync. File sharing is covered by Tiki file galleries
See also