New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
want to know too
I tried both a bit for a side project. SeaweedFS was too complicated for me to get up-and-running, so I abandoned it again. I do have to say that while reading the documentation it seemed very well documented and capable. I just ran out of time and will to continue setting up all the IPs and ports through my VPN.
Garage setup is easier, just download the binary, create the garage.toml file (it has only a handful of options) and run it. Node linking is really easy, although it also needs a bit of port forwarding. By that time I was using nebula (mesh) VPN so it was much easier, maybe with nebula I would have kept on using SeaweedFS, who knows.
I like the garage "gateway" feature, where you can add a node/server to the cluster that does not store data but has access to it. Gateway mode creates a locally-hosted S3 interface running over http (unencrypted), but the data is exchanged over the encrypted garage gRPC link. That way, you don't need to bother with TLS certificates or S3 behind a reverse proxy, but internet traffic is still encrypted.
I abandonded garage later on though, because I was not satisfied with the write performance. There seemed to be some write amplification in my case that reduced the effective write speed to less than a third of what should be possible, and by that time I couldn't be bothered to dig into the issue.
I'm now storing my data over SFTP instead of S3 again and onto a single node instead of immediately-replicated and resorted to nightly synchronisations onto my other nodes instead.