3 ms·
> I agree that "object" makes no sense when applied to S3. It's not like you can store an "account" object and call a method to get back the current balance, w
by Goladus 11y ago
> I agree that "object" makes no sense when applied to S3. It's not like you can store an "account" object and call a method to get back the current balance, with accrued interest for the time since last deposit added in. Or even store an image and call a method to get back a black-and-white version. Etc.
Well, yes, they aren't OOP objects. But as you say, "files" isn't great either. But it was a theoretical alternative. For example, you could do a search/replace on the S3 docs here: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects.html http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects...., and they would still make sense.
But FTP isn't even close. You could not find/replace "Object" with "FTP" without making those docs completely incoherent.
- apetresc 11y ago> But FTP isn't even close. You could not find/replace "Object" with "FTP" without making those docs completely incoherent. That's the wrong comparison though. You could replace all instances of "S3" with "an FTP server" and it would make a ton of sense, minus the reliability claims.
- Goladus 11y agoNo, it wouldn't make any sense at all. Amazon Unlimited FTP Server is a simple key, value store designed to store as many FTP Servers as you want. You store these FTP Servers in one or more buckets. An FTP Server consists of the following: You could use a mix of "FTP Server" and File: Amazon Unlimited FTP Server is a simple key, value store designed to store as many files as you want. You store these files in one or more buckets. A file consists of the following: Note that this is essentially redefining the word file to include S3-specific metadata.