S3 is files, but not a filesystem

Post by paranoidrobot » Sun, Mar 10, 2024, 6:09 AM UTC

nostrebored wrote: post #8

leetrout wrote: post #3

My big pet peeve is AWS adding buttons in the UI to make "folders". It is also a fiction! There are no folders in S3. > When you create a folder in Amazon S3, S3 creates a 0-byte object with a key that's set to the folder name that you provided. For example, if you create a folder named photos in your bucket, the Amazon S3 console creates a 0-byte object with the key photos/. The console creates this object to suppor…

Weird that it says folders now. I remember it being very strictly called a prefix when I was at AWS.

Post by winwang » Sun, Mar 10, 2024, 6:10 AM UTC

solumunus wrote: post #6

leetrout wrote: post #3

My big pet peeve is AWS adding buttons in the UI to make "folders". It is also a fiction! There are no folders in S3. > When you create a folder in Amazon S3, S3 creates a 0-byte object with a key that's set to the folder name that you provided. For example, if you create a folder named photos in your bucket, the Amazon S3 console creates a 0-byte object with the key photos/. The console creates this object to suppor…

What exactly do you think a folder is? It’s just an abstraction for organising data.

Post by fiddlerwoaroof » Sun, Mar 10, 2024, 6:13 AM UTC

klodolph wrote: post #9

riehwvfbk wrote: post #5

Earlier quoted context omitted.

Is that really so different from how folders work on other systems? A directory inode is just an inode.

Yes. It is, in practice, incredibly different. Imagine you have a file named /some/dir/file.jpg. In a filesystem, there’s an inode for /some. It contains an entry for /some/dir, which is also an inode, and then in the very deepest level, there is an inode for /some/dir/file.jpg. You can rename /some to /something_else if you want. Think of it kind of like a table: +-------+--------+----------+-------+ | inode | paren…

Post by Twirrim » Sun, Mar 10, 2024, 6:18 AM UTC

Post by mickael-kerjean » Sun, Mar 10, 2024, 6:20 AM UTC

fiddlerwoaroof wrote: post #14

3weeksearlier wrote: post #2

I dunno, are features like partial file overwrites necessary to make something a filesystem? This reminds me of how there are lots of internal systems at Google whose maintainers keep asserting are not filesystems, but everyone considers them so, to the point where "_____ is not a filesystem" has become an inside joke.

Yeah, it’s sort of funny how “POSIXish semantics” has become our definition of these things, when it’s just one kind of thing that’s been called a filesystem historically.

  type IBackend interface {
    Ls(path string) ([]os.FileInfo, error)
    Cat(path string) (io.ReadCloser, error)
    Mkdir(path string) error
    Rm(path string) error
    Mv(from string, to string) error
    Save(path string, file io.Reader) error
    Touch(path string) error
  }