ObjectiveFS VS Google Cloud Filestore

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 / 8 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: 10 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

It's basically still the only game in town for a high performance shared posix filesystem with multiple writers and builtin support in basically all operating systems. As an application developer, I probably wouldn't choose to design a system that needed it. However there are lots of good reasons why a company in 2023 might decide to use this NFS based product: https://cloud.google.com/filestore?hl=en. - Source: Hacker News / 5 months ago

Hi, Brandon from GCS here! If you're looking for all of the guarantees of a real, POSIX filesystem, you want to do fast top level directory listing for 100MM+ nested files, and POSIX permissions/owner/group and other file metadata are important to you, Gcsfuse is probably not what you're after. You might want something more like Filestore: https://cloud.google.com/filestore Gcsfuse is a great way to mount Cloud... - Source: Hacker News / 8 months ago

At Redactics we needed a way to provide writeable persistent storage to multiple Kubernetes pods. Cost effective ReadWriteMany storage options are generally somewhat limited, in our experience. Using Amazon S3 or the like was also not a great option for us, because the Redactics SMART Agent uses Apache Airflow and the KubernetesPodOperator for a number of its workflow steps - many of which run in parallel. This... - Source: dev.to / over 1 year ago

It sounds like you're looking for Filestore. You can mount Filestore shares as NFS in GKE deployments, and every deployment sees the same set of files. Source: almost 2 years ago