Hacker News new | ask | show | jobs
by jamesblonde 69 days ago
S3 Files was launched today without support for atomic rename. This is not something you can bolt on. Can you imagine running Claude Code on your S3 Files and it just wants to do a little house cleaning, renaming a directory and suddenly a full copy is needed for every file in that directory?

The hardest part in building a distributed filesystem is atomic rename. It's always rename. Scalable metadata file systems, like Collosus/Tectonic/ADLSv2/HopsFS, are either designed around how to make rename work at scale* or how work around it at higher levels in the stack.

* https://www.hopsworks.ai/post/scalable-metadata-the-new-bree...
2 comments
thomas_fa 69 days ago
Indeed this is not an easy problem. And our s3-compatible system do support the atomic rename with extended protocol in a graceful way, see the demo with our tool [1].

[1] https://github.com/fractalbits-labs/fractalbits-main/tree/ma...

link
jamesblonde 69 days ago
We have advanced to building S3 stores with claude code - impressive:

https://github.com/fractalbits-labs/fractalbits-main/graphs/...

link
sb-gcs 68 days ago
Hierarchical Namespace buckets in Google Cloud Storage support folder operations, including atomic folder renames.

https://docs.cloud.google.com/storage/docs/hns-overview#feat...

link