With S3QL, you access you data only via S3QL. You would no more directly
access data in the Swift object storage than you would directly access
the data on /dev/sda1 if you were using a traditional filesystem. A file
on an S3QL filesystem does not map to an object in the underlying
storage (Swift). This allows S3QL to do things like de-duplicate blocks
and to have semantics much closer to a traditional filesystem.
Also, S3QL supports being mounted from at most one computer at a time.
S3FS presents S3 objects as files. If you put a file in S3FS, it'll be
available as a single S3 object. I think you can also have multiple S3FS
mounts of the same S3 objects, on different computers. S3FS does not act
like a traditional filesystem in a bunch of ways (see the "Limitations"
sections in their readme).
rclone is similar to S3FS.
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/4a959504-491a-d061-ff55-b7db983c907a%40metrics.net.
