For workloads with many small files, it usually is better to store many files in a single object. Filesystems with regular POSIX semantics, such as atomic directory renames etc, also makes it easier to integrate with existing software. We have seen a lot of scientific computing usage of our filesystem (https://objectivefs.com) and as you mentioned localized caching of the working set is key to great performance. - Source: Hacker News / 9 months ago

Since this seems to be the crowd that would appreciate it - https://objectivefs.com/ is another good "shared files" option, it uses s3 in the background but has a client in the foreground that caches and checks for when/how to update s3 to minimize transfers and boost performance. Source: 11 months ago

Object storage is a higher-level abstraction than block-storage. FUSE and similar tech can do the job for basic requirements like read-only access by legacy applications but rarely works well for other scenarios. Object storage can be used decently well if there's more complex layer in between like https://objectivefs.com/. - Source: Hacker News / about 1 year ago

... Or does "S3 file system" mean https://github.com/awslabs/mountpoint-s3 - a Rust project by AWS Labs that provides "a simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system" ? - Source: Hacker News / 2 months ago

Mountpoint-s3 is AWS’ first party solution for mounting s3 buckets as file systems: https://github.com/awslabs/mountpoint-s3 Haven’t used it but it looks cool, if a bit immature. - Source: Hacker News / 9 months ago