Question: Amazon S3-backed content addressable blob store

[dweinstein]

@mafintosh thx for the cool project.

I have a branch in my fork here that uses a fork of s3-blob-store (my feature branch adds a move primitive to the s3-blob-store, hope it gets upstreamed) as a "backing" store rather than the local filesystem.

Do you have any suggestions on whether and how this might be useful? ISTM that it might be possible to pass the backing store as an option as long as we abstract over the mkdirp and unlink stuff. Also instead of calling things a dir I use prefix.

Before I go thru the trouble I thought I'd ask if you're interested in this. otherwise I'll just maintain the "s3-content-addressable-blob-store" separately for my immediate needs.

Thanks!

[bcomnes]

My 2¢: s3-content-addressable-blob-store would be appropriate as a stand alone package and you should add it to at the abstract blob store example list if you plan on supporting it. Perhaps link to it from this repos readme as well. Loose coupling by default ftw.

[bcomnes]

Also #15 would maybe resolve this.