2nd
2007
S3, then ftp, then OmniDrive, then Gmail?
In our last post, we discussed Bandwagon’s storage agnostic approach. To that end, we want to share some of our upcoming plans and get feedback.
We define Internet-based storage as cloud types. S3 is one cloud type, ftp is yet another, etc. We futher define each cloud type with a cloudid, a one-to-many approach. Logically, S3 should only have one cloudid…how many people will have different S3 accounts? A similar argument could be made to OmniDrive.
However, with ftp and Gmail, customers could have multiple ftp accounts and (most definitely) multiple Gmail accounts to store their stuff. To that end, how do we approach the relationship of which items/files to store onto which cloud type and/or cloudids?
For example, let’s say I have 1 S3 account, 2 ftp accounts and 3 Gmail accounts. Do we store the Celine Dion song on the S3 account or ftp or Gmail account?
One approach is to just randomize. Another approach is to ask the customer which cloudid to “fill up” first with a max storage setting. However, asking the customer would require an additional interface/step. Is the tradeoff worth it? Is there a better approach?
S3 has a permancence to it. OmniDrive as well. But ftp accounts can be changed or Gmail accounts deleted.