28
edits
Object Store Quick Start: Difference between revisions
Jump to navigation
Jump to search
Basic description of an Obj Store
(Basic description of an Obj Store) |
|||
| Line 11: | Line 11: | ||
The object store maintains its own set of credentials. | The object store maintains its own set of credentials. | ||
== What an Object Store is and isn't == | |||
(from https://github.com/s3fs-fuse/s3fs-fuse?tab=readme-ov-file#limitations) | |||
Generally, an Object Store cannot offer the same performance or semantics as a local file system. More specifically: | |||
* random writes or appends to files require rewriting the entire object, optimized with multi-part upload copy | |||
* metadata operations such as listing directories have poor performance due to network latency | |||
* non-AWS providers may have eventual consistency so reads can temporarily yield stale data (AWS offers read-after-write consistency since Dec 2020) | |||
* no atomic renames of files or directories | |||
* no coordination between multiple clients mounting the same bucket | |||
* no hard links | |||
* inotify detects only local modifications, not external ones by other clients or tools | |||