Top Themes from the Discussion
| # | Theme | Supporting Quote |
|---|---|---|
| 1 | EFS caching & cost concerns | > "Zero mention of s3fs which already did this for decades." — mgaunard > "EFS as a eventually consistent cache in front of S3." — PunchyHamster > "They found a way to make money on it by putting a cache in front of it. Less load for them, better performance for you. Maybe you save money, maybe you dont." — LazyMans |
| 2 | Comparison to existing solutions & skepticism about novelty | > "This is pretty different than s3fs. s3fs is a FUSE file system that is backed by S3." — the8472 > "I was thinking: “No way this has existed for decades”. But the earliest I can find it existing is 2008. Strictly speaking not decades but much closer to it than I expected." — the8472 > "Good point. There's a wide gulf between being able to design your workflow for S3 and trying to map an existing workflow to it." — themafia |
| 3 | Consistency & atomic‑operation challenges | > "When S3 Files detects the conflict, it moves your version of report.csv to the lost and found directory and replaces it with the version from the S3 bucket." — rdtsc > "Files can be immutable if you have mutable metadata – but S3 does not have mutable metadata, so you can't rename a directory without a full copy of all its contents." — jamesblonde |
All quotations are taken verbatim from the participants, enclosed in double quotes and attributed to the respective usernames.